feat: support form versioning#390
Open
craigzour wants to merge 9 commits into
Open
Conversation
craigzour
force-pushed
the
feat/form-response-versioning
branch
from
647f8f7 to
40a7534
Compare
… specific form version
…that feature by default
…nnecessary logs when running tests
craigzour
force-pushed
the
feat/form-response-versioning
branch
2 times, most recently
from
4c0cca0 to
ff3c40f
Compare
…ersions that are not flagged as vulnerable
craigzour
force-pushed
the
feat/form-response-versioning
branch
from
ff3c40f to
8dcb61c
Compare
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.
Summary | Résumé
versionproperty to API response when retrieving new form submissionsversionproperty to API response when retrieving specific form submission?version=<version>query parameter to the form template retrieval endpoint, allowing clients to request a specific version of a form.vitest-tsconfig-pathspackage now that Vitest supports TSConfig paths by defaultblockExoticSubdepsandminimumReleaseAge)esbuildandform-datadependencies to force use specific versions that are not flagged as vulnerable by our systemNote: this PR does not include any changes to the API doc or API examples because as we are still in early development stage.