New UUIDs #514
Merged
New UUIDs #514
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
And extend config migration code to properly handle this.
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #514 +/- ##
==========================================
+ Coverage 85.09% 85.50% +0.41%
==========================================
Files 51 51
Lines 1992 2035 +43
Branches 335 343 +8
==========================================
+ Hits 1695 1740 +45
+ Misses 234 224 -10
- Partials 63 71 +8 |
Merged
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.
Adds support for UUID version 6, 7, and 8. Technically, those are currently only in the draft phase, but my understanding is that their specifications are unlikely to change.
Fixes #513.
Additionally, I renamed the
typefield of theUuidSchemetoversion, because that's more accurate; user configs are migrated automatically using the API introduced in #464. Since this is the first time I actually used that API, I also fixed some usability and clarity issues and added more utility methods.(I also snuck in a little bug fix.)