Skip to content
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

UX Improvement: Settings main menu list ID. #3

Open
phil9690 opened this issue Nov 6, 2018 · 1 comment
Open

UX Improvement: Settings main menu list ID. #3

phil9690 opened this issue Nov 6, 2018 · 1 comment
Labels
feature-request New feature or request

Comments

@phil9690
Copy link

phil9690 commented Nov 6, 2018

Description of issue

In the settings the page you need to know the ID of the list you want to use for the main menu. This should be a dropdown of all lists that are links, so that a user can easily change this without having to find the list id.

Current behaviour

Have to input ID value into text box

Expected behaviour

Drop down with all valid lists available for selection.

@patricklindsay
Copy link
Member

The settings area is currently for admins (developers) only. It's super basic, there isn't any validation of the fields and they're all text.

Ideally there would be a pattern of registering settings to each of the particular areas, when registering you could pass in the type of setting and validations. Using this we'd then be able to create the appropriate behaviour i.e. for a setting which expects a list ID display dropdown of all visible lists; for a setting which expects an image display to the user a link to the image selector.

This would be nice to implement, but given that the area is locked down to admins and is pretty much only used for setup it isn't much of a priority.

@patricklindsay patricklindsay added the feature-request New feature or request label Nov 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants