fix(konsistent): represent exact TypeScript type references as string alternatives to JSON Schema shapes - #96
Merged
Conversation
… interpolated values plus clearly separate them from JSON schema object definitions
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
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.
Pull Request Description
TypeScript type references in constant and type schemas overloaded JSON Schema's
typeproperty and rejected interpolated references. This separates exact TypeScript references from JSON Schema objects so references can use the same templates as other predicate strings.Relevant technical choices
Checklist
pnpm changesetin the project root if package files were modified)