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
Current
Users configure the decorators for each attribute in a separate part of the Manage page from where they configure the corresponding attributes.
Proposed
I think users should configure decorators within the editing modal for the corresponding attribute. Is the issue here that that would crowd the modal?
The text was updated successfully, but these errors were encountered:
There are four reasons why I didn't do this, three UX and one practical:
I suspect users will often want to edit decorators in bulk; having to go individually into each attribute and re-specify attribute values feels like a pain. In my mind it makes sense to think about all the decorators together.
I also think that it would indeed make the editor window crowded.
Decorators should be a rarely used feature; to the extent possible, I think we should remove them from the regular user flow.
It'd mean that we'd need to create popup modals for editing core attributes, which is a bit of a pain; it'd also require refactoring the Phoenix form, which would be annoying.
Closing for now but reopen if this explanation is not compelling and/or you feel strongly that it needs to be in the attribute editor.
Current
Users configure the decorators for each attribute in a separate part of the Manage page from where they configure the corresponding attributes.
Proposed
I think users should configure decorators within the editing modal for the corresponding attribute. Is the issue here that that would crowd the modal?
The text was updated successfully, but these errors were encountered: