fix(dfn): fix schema version migrations#327
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backwards-compatibility fixes, schema version naming/differentiation, and usability improvements.
migratesubcommand to DFNs CLI1: original DFNs, flat set of components, each a flat list of fields plus comment lines2.0.0.dev0: flat set of components, some structuring of fields, consumed by flopy32.0.0.dev1: tree of components, more extensive field structuring, consumed by flopy42.0.0.dev2: pydantic redesign, flat set of components, structured blocks/fieldsCloses #259. The
modflow_devtools.dfnmodule stays stable and supports only the2.0.0.dev0schema version expected by flopy3. The newdfnsmodule gets some improvements and supports all three prototype schema versions. This versioning schema can continue until we release version 2.