Skip to content
This repository has been archived by the owner on Dec 21, 2019. It is now read-only.

Externalize constraints #88

Open
edgarmueller opened this issue Dec 19, 2016 · 2 comments
Open

Externalize constraints #88

edgarmueller opened this issue Dec 19, 2016 · 2 comments
Labels
enhancement

Comments

@edgarmueller
Copy link
Contributor

When using the library in order to build up a JSON schema AST using constraints (e.g. to be emitted as JSON), one needs access to internal packages.
@edgarmueller edgarmueller added this to the 0.8.7 milestone Dec 19, 2016
@edgarmueller
Copy link
Contributor Author

edgarmueller commented Dec 19, 2016 •
edited
Loading

Also, before externalizing, one should replace schemaTypeAsString with an appropriate boolean for each schema type. Currently, one can provide invalid values for the type keyword since it expects a string.

@edgarmueller
Copy link
Contributor Author

Another related issue: booleanWriter does delegate directly to anyConstraintWriter as it should be and hence always includes the type in the serialization.

@edgarmueller edgarmueller modified the milestones: 0.8.8, 0.8.7 Feb 5, 2017
@edgarmueller edgarmueller removed this from the 0.8.8 milestone Mar 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@edgarmueller