-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make saved / needs saving state more obvious in the admin #27
Labels
Comments
The buttons have been renamed in the 0.3.x releases to make them a bit more explanatory, but there's still no "disabled" style indicating that everything is saved. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently when you edit a field, nothing tells you if you need saving. The save button itself is called "edit field" which is very unintuitive. The button should really be disabled until you make a change.
When creating the field types I added an autosave feature when you edit the dropdown type so that if you believe "add" saves the field, well it does... But you should actually be hitting "edit field" to have the new options list saved.
The text was updated successfully, but these errors were encountered: