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

[old] refactor: A Better API for Derived Settings #36132

Conversation

kdmccormick
Copy link
Member

@kdmccormick kdmccormick commented Jan 17, 2025

See: #36192

robrap and others added 8 commits January 17, 2025 16:16
This reintroduces commit 1593923,
which was reverted due to a typo.

The typo is fixed in the commit immediately following this one.

Co-Authored-By: Feanil Patel <feanil@axim.org>
Some of our settings depend on the values of other settings.  Rather
than explicitly looking up each one in the YAML settings file, we can
simply derive them based on the setting in the YAML file after all the
YAML settings have been loaded.
This was a little hard to grok so I added a little example to make it
easier to understand.
@kdmccormick kdmccormick force-pushed the kdmccormick/derived-better branch from 0c5dd5e to b0fa9ac Compare January 29, 2025 15:36
@kdmccormick kdmccormick changed the title refactor: A Better API for Derived Settings [old] refactor: A Better API for Derived Settings Jan 29, 2025
@kdmccormick
Copy link
Member Author

Closed in favor of a PR against master: #36192

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.

3 participants