-
Notifications
You must be signed in to change notification settings - Fork 99
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
Begin config migration #1123
Begin config migration #1123
Conversation
This doesn't compile so makes workspace level changes annoying to check
This isn't used anywhere
8d291d6
to
3a05306
Compare
Build Succeeded 🥳 Build Id: 8786dff1-433f-435a-835b-cf14196842ee The following development images have been built, and will exist for the next 30 days: To build this version:
|
} | ||
|
||
#[cfg(test)] | ||
impl<'de> Deserialize<'de> for Config { |
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.
Any reason for the manual impl over a derive?
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.
Because the dynamic config will require manual deserialization so just getting it out of the way now.
dyn_cfg: DynamicConfig { | ||
id: default_id(), | ||
version: Version::default(), | ||
typemap: default_typemap(), | ||
}, |
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.
Is there a reason DynamicConfig doesn't impl default?
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.
Not really, will probably add it eventually.
DynamicConfig
as a field ofConfig
id
andversion
toDynamicConfig
<C: Serialize>
as it only cares about dumping the config as JSONPart of #1117