Support readOnly property from latest validation draft
#1282
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
9 tasks
pahen
changed the title
readOnly property from latest validation draft
epicfaace
requested changes
May 13, 2019
|
Would it be possible to have a new release with this included soon? |
|
Is there any plan for a new release soon @epicfaace? I really need this feature. |
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.
Reasons for making this change
Since the
readOnlyproperty now is available in the latest validation draft (previously it was in hyper schema only), it makes sense to use this property to signal read only for fields.Fixes #976
Replaces PR #888
Checklist
npm run cs-formaton my branch to conform my code to prettier coding style