feature: add postgraphile-tag-json-tools for json schema generation #206
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.
Like requested in #205
Description
This PR only uses the
createJsonSchema
part ofpostgraphile-tag-json-tools
, asextractSmartTags
andloadSmartTags
functionalities do not seem necessary here.Changes in the database will update
@app/server/pg-database-smart-tags.schema.json
, but edits in@app/server/pg-smart-tags.schema.json
will persist, so additional tags can be added without fear of something being overridden. (I added simpleCollections and resultFieldName, as I didn't have those in my initial schema - if you can think of any more tags, please mention them & I will add them.)I've marked the place to add new tags with
"$comment": "------ Add extra tags here, in
properties. ------",
.Performance impact
None in production use, probably neglectable in dev mode.
Security impact
None in production use, nothing I could think of in dev use.
Checklist
yarn lint:fix
passes.yarn test
passes.RELEASE_NOTES.md
file (if one exists).