You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update: It looks like edit compute / infra / provider also has the same problem. It looks like most edit pages using the same react code may have this problem.
Also, the list views have the problem in the next comment with %s when checking ✅ one of them in the list/or selecting all.
Rails 7.0 and 7.1 have this same problem:
Warning: React does not recognize the %s prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase %s instead. If you accidentally passed it from a parent component, remove it from the DOM element.%s,loadingMessage,loadingmessage, in select (created by Select) in div (created by Select) in div (created by Select) in div (created by Select) in Select (created by ClearedSelect) in ClearedSelect (created by Select) in Select (created by Select) in Select (created by SelectWithOnChange) in SelectWithOnChange (created by SingleField) in FormFieldHideWrapper (created by SingleField) in FormConditionWrapper (created by SingleField) in SingleField (created by FormRenderer) in form (created by Form) in Form (created by Form) in Form (created by FormTemplate) in FormTemplate (created by WrappedFormTemplate) in WrappedFormTemplate in Unknown (created by ReactFinalForm) in ReactFinalForm (created by FormRenderer) in FormRenderer (created by MiqFormRenderer) in MiqFormRenderer (created by Connect(MiqFormRenderer)) in Connect(MiqFormRenderer) (created by ProviderForm) in div (created by ProviderForm) in ProviderForm in Provider
EDIT: This also occurs when editing ansible repositories, ansible credentials, etc.
The text was updated successfully, but these errors were encountered:
Not sure if it's related. If you "check" one of the ansible tower automation managers, you get a similar error on component %s.
Warning: Cannot update a component (%s) while rendering a different component (%s). To locate the bad setState() call inside %s, follow the stack trace as described in https://fb.me/setstate-in-render%s,MiqToolbar,GtlView,GtlView, in GtlView in Provider
jrafanie
changed the title
Edit automation -> providers - Ugly React warning %s prop on DOM element
Edit automation -> providers - Ugly React warning %s prop on DOM element in DEVELOPMENT mode
Feb 26, 2025
Update: It looks like edit compute / infra / provider also has the same problem. It looks like most edit pages using the same react code may have this problem.
Also, the list views have the problem in the next comment with %s when checking ✅ one of them in the list/or selecting all.
Rails 7.0 and 7.1 have this same problem:
Warning: React does not recognize the
%s
prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase%s
instead. If you accidentally passed it from a parent component, remove it from the DOM element.%s,loadingMessage,loadingmessage, in select (created by Select) in div (created by Select) in div (created by Select) in div (created by Select) in Select (created by ClearedSelect) in ClearedSelect (created by Select) in Select (created by Select) in Select (created by SelectWithOnChange) in SelectWithOnChange (created by SingleField) in FormFieldHideWrapper (created by SingleField) in FormConditionWrapper (created by SingleField) in SingleField (created by FormRenderer) in form (created by Form) in Form (created by Form) in Form (created by FormTemplate) in FormTemplate (created by WrappedFormTemplate) in WrappedFormTemplate in Unknown (created by ReactFinalForm) in ReactFinalForm (created by FormRenderer) in FormRenderer (created by MiqFormRenderer) in MiqFormRenderer (created by Connect(MiqFormRenderer)) in Connect(MiqFormRenderer) (created by ProviderForm) in div (created by ProviderForm) in ProviderForm in ProviderEDIT: This also occurs when editing ansible repositories, ansible credentials, etc.
The text was updated successfully, but these errors were encountered: