add high-level validator serialization API#117
Closed
srivastava-diya wants to merge 1 commit into
Closed
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
1 participant
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
Resolves #112
This PR introduces a first-class, high-level API for validator serialization, allowing users to cleanly serialize and restore validators without interacting directly with the low-level AST.
Changes included:
.serialize()method directly to the validator function returned byvalidate().restoreValidator(json)API that deserializes the AST and reconstructs the validator by resolving its evaluation plugins.DeserializeOptionstype andoptionsparameters, aspluginsByIdis no longer required with the new approach.lib/restore-validator.spec.ts) to ensure the high-level API behaves correctly.