[MAJOR] Many changes for Conformity 2.0 (WIP) #89
Conversation
This file contains 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
…ed utils and currency fields.
…ethod to Validation type.
…alidation to better handle variable key fields.
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.
Conformity 2.0 will be the next major release of Conformity. The primary goals we aim to achieve with this major version are:
To facilitate migration from 1.x to 2.0, we have deprecated (not removed) many common 1.x APIs and fields. As such, most projects currently utilizing Conformity 1.x should continue to work without modifications upon upgrading to 2.0. However, breaking changes do exist. These will be detailed in a soon-to-be-written migration document.