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
Describe the bug
If a field inside a collapsed object fires a validation error, the entry will not be saved. This is the correct behavior, but the problem is, that there is no indication of where the error occurs.
To Reproduce
Steps to reproduce the behavior. For example:
Create an object field and add collapsed: true
Add a required sub-field
Leave the sub-field empty and try to save the entry.
See a general error notification at the top and observe that there is no notification on the collapsed object
Expected behavior
If a field is collapsed and it includes objects with validation errors, it should also be treated as a field with an error. It should get a red border and an explanation text in red color.
Screenshots
Collapsed - there is no indication that a required filed is empty in services object
Uncollapsed
Applicable Versions:
Netlify CMS version: 2.10.147
Git provider: GitHub
OS: MacOS 11.4 (20F71)
Browser version: Brave 1.26
CMS configuration
Example configuration for a collapsed object with a required string field. This happens on any global configuration I believe.
Describe the bug
If a field inside a collapsed object fires a validation error, the entry will not be saved. This is the correct behavior, but the problem is, that there is no indication of where the error occurs.
To Reproduce
Steps to reproduce the behavior. For example:
collapsed: true
Expected behavior
If a field is collapsed and it includes objects with validation errors, it should also be treated as a field with an error. It should get a red border and an explanation text in red color.
Screenshots
Collapsed - there is no indication that a required filed is empty in services object
Uncollapsed
Applicable Versions:
CMS configuration
Example configuration for a collapsed object with a required string field. This happens on any global configuration I believe.
The text was updated successfully, but these errors were encountered: