Add validation framework exceptions and pydantic utilities#5403
Draft
SajidAlamQB wants to merge 1 commit intomainfrom
Draft
Add validation framework exceptions and pydantic utilities#5403SajidAlamQB wants to merge 1 commit intomainfrom
SajidAlamQB wants to merge 1 commit intomainfrom
Conversation
Signed-off-by: Sajid Alam <sajid_alam@mckinsey.com>
7 tasks
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.
Description
First in a series of PRs implementing the parameter validation framework (#5313). This PR adds the exceptions and utility functions that all subsequent validation components depend on.
See #5313 for the full implementation plan and architecture diagram.
PR chain:
PR 1: Exceptions + utils (this PR)
PR 2: Source filters + tests
PR 3: Model factory + tests
PR 4: Type extractor + tests
PR 5: Parameter validator + tests
PR 6: Context integration + tests
Development notes
Developer Certificate of Origin
We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a
Signed-off-byline in the commit message. See our wiki for guidance.If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.
Checklist
RELEASE.mdfile