-
-
Notifications
You must be signed in to change notification settings - Fork 228
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
Use Configy to read user settings (settings.json
) too
#2343
Conversation
settings.json
) too
093d064
to
21ae75f
Compare
Rebased, should be G2G, let's see what the CI says. |
Hold on, there's one thing I forgot to tackle: Error handling. |
b8ff4e1
to
13c1d73
Compare
This will provide superior error messages to the user, and match what we already do for `dub.selections.json`. It also allows us to remove many fields from the `Dub` class. Those fields existed so that we would not have to re-compute the data from the JSON DubConfig was storing. Now that we use a simple struct, and do the aggregation eagerly, all of that complexity can go.
13c1d73
to
4169769
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but feel free to first add the error handling you wanted to add
I actually tested it yesterday and the error handling LGTM. It's not colored but all the information is here. |
Depends on #2310First step towards #1832
Only the last two commits belong to this PR.
Once #2310 and this are merged, adding settings will be massively simpler.
I am thinking of holding back on #1832 so that we can come up with a "clean" format for the YAML settings, and it will make writing conversion code (from
settings.json
tosettings.yaml
) much simpler.