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.

Sign up for GitHub

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

Jump to bottom

More compatibility in config #52

Open
JasonGross opened this issue Feb 19, 2024 · 0 comments
Open

More compatibility in config #52

JasonGross opened this issue Feb 19, 2024 · 0 comments
Labels
engineering priority: medium-low Non-blocking but somewhat time-sensitive, e.g., adds overhead or friction

Comments

@JasonGross
Copy link
Owner

It should be possible to design config to be backwards compatible, in particular to the following two cases:

  1. adding a field where the default value does not change the current behavior should not invalidate hashes, and should support loading from previous versions of the config
  2. it should be possible to rename a field and add a deprecated alias (as an __init__ argument? or in some other way?) and indicate to the hashing function that the old name should be used for hashing, and it should be possible to load configs from the old format
@JasonGross JasonGross added engineering priority: medium-low Non-blocking but somewhat time-sensitive, e.g., adds overhead or friction labels Feb 19, 2024
@JasonGross JasonGross mentioned this issue Feb 19, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
engineering priority: medium-low Non-blocking but somewhat time-sensitive, e.g., adds overhead or friction
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JasonGross