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
The configuration components and resource components in a module configuration should be either of the "General Configuration" schema, or a custom schema with a flat list of text fields.
When I tried to have a multivalue embedded field in a custom resource component I noticed that the settings page has published the field in a weird way, the value of the field is an object id. This is what I found in the [modulename].json
I guess that this means that the TBB rendering this file is not checking the field type at all. It should handle the situation and not render the object id.
I think it is best when the Settings page would raise an publishing error whenever there are unsupported fields in the configuration or resource components.
The text was updated successfully, but these errors were encountered:
The configuration components and resource components in a module configuration should be either of the "General Configuration" schema, or a custom schema with a flat list of text fields.
When I tried to have a multivalue embedded field in a custom resource component I noticed that the settings page has published the field in a weird way, the value of the field is an object id. This is what I found in the
[modulename].json
I guess that this means that the TBB rendering this file is not checking the field type at all. It should handle the situation and not render the object id.
I think it is best when the Settings page would raise an publishing error whenever there are unsupported fields in the configuration or resource components.
The text was updated successfully, but these errors were encountered: