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

Provide ordering to configuration settings #1530

Merged
merged 4 commits into from
Feb 6, 2019

Conversation

kylebarron
Copy link
Contributor

Hydrogen has grown to the point where there are 14 configuration settings. Currently, no ordering is provided, so I think they're ordered alphabetically in terms of the config key. I think this is more confusing than it has to be for users.

This PR attempts to group settings logically and then order them with the order value in the dictionary. The idea is "general settings" then "output settings" then "kernel settings", and within each ordered by most used to least used.

The order is:

  • autocomplete
  • showAutocompleteFirst
  • statusBarDisable
  • debug
  • autoScroll
  • outputAreaDefault
  • outputAreaDock
  • outputAreaFontSize
  • globalMode
  • kernelNotifications
  • startDir
  • languageMappings
  • startupCode
  • gateways

Copy link
Member

@BenRussert BenRussert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really great idea to clean this up, thanks! I will wait to merge until you see my comments on #1515.

@BenRussert
Copy link
Member

If you are still up ping me on slack real quick @kylebarron, I can help you get this rebased cleanly. We could do that tomorrow if you are out for the night.

@kylebarron
Copy link
Contributor Author

I think after merging now-current master it'll pass tests and be fine

@kylebarron kylebarron merged commit f2eadb9 into nteract:master Feb 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants