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 issue is that when you flip screen sizes the auto value requires some analysis to find a field you want to change. I think visually it would be better if you could see the component instead of what it is currently e.g. "auto: false"
My thought with this is:
you would render the the field component (e.g. the toggle component instead of auto: false)
you would lower the opacity of the component to indicate it's an auto value - non auto values will stand out this way
you would show a chain link icon to the left of the component showing it is linked
hovering over the component will lower the opacity more and overlay the text "set value" centered horizontally and vertically
clicking on "set value" will show it the way it currently shows an overwritten auto value with the revert icon
The text was updated successfully, but these errors were encountered:
This is probably considered a bug too. When you use an inline type field and store an object as the value it renders as [Object object] for auto values
timoconnellaus
changed the title
Improvement: auto values are hard to follow when you flip between screen sizes
Improvement (bug in some contexts): auto values are hard to follow when you flip between screen sizes
Jun 14, 2024
The issue is that when you flip screen sizes the auto value requires some analysis to find a field you want to change. I think visually it would be better if you could see the component instead of what it is currently e.g. "auto: false"
My thought with this is:
The text was updated successfully, but these errors were encountered: