You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The update breaks configurations because of dtolnay/serde-yaml#342 - the suggestion may need to be used with a special with wrapper to work with Vec<Enum> and other container types 😞
(the better approach may be to bake it into the Deserialize impl somehow?)
The issue here is that with the update the config is no longer compatible with json parsed as yaml, as it will then rely on the yaml-exclusive !tag feature. Alternatively, just switch to serde-json instead and give up on user-readable configs? Or support both via file extension and/or other option?
The update breaks configurations because of dtolnay/serde-yaml#342 - the suggestion may need to be used with a special
with
wrapper to work withVec<Enum>
and other container types 😞(the better approach may be to bake it into the
Deserialize
impl somehow?)The issue here is that with the update the config is no longer compatible with json parsed as yaml, as it will then rely on the yaml-exclusive
!tag
feature. Alternatively, just switch to serde-json instead and give up on user-readable configs? Or support both via file extension and/or other option?EDIT: singleton_map_recursive is what you actually want, to work around
Vec
issuesThe text was updated successfully, but these errors were encountered: