Repository navigation
feat(schema): add doc comment support for element-typed array fields - #79
Merged
Merged
Conversation
1- Add DOC_COMMENT token type and lexer handling for /// comments, attaching each comment to the following field declaration 2- Add peekAhead(n) so comment skipping can distinguish /// from // 3- Add DefaultArray kind with ArrayValues to resolve @default([]) 4- Add extractDocCommentElementType() and docCommentElementTypeMap to map Prisma element types to Go types for @ElementType hints 5- Resolve @ElementType fields as arrays (IsArray + []T GoType) for JSON-backed array storage 6- Add guardrail to only allow the @ElementType to reach the client IF field type is JSON, basically a sentinel to declare sqlite phantom arrays
…ield type is JSON, basically a sentinel to declare sqlite phantom arrays
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.
1- Add DOC_COMMENT token type and lexer handling for /// comments, attaching each comment to the following field declaration
2- Add peekAhead(n) so comment skipping can distinguish /// from //
3- Add DefaultArray kind with ArrayValues to resolve @default([])
4- Add extractDocCommentElementType() and docCommentElementTypeMap to map Prisma element types to Go types for @ElementType hints
5- Resolve @ElementType fields as arrays (IsArray + []T GoType) for JSON-backed array storage
6- Add guardrail to only allow the @ElementType to reach the client IF field type is JSON, basically a sentinel to declare sqlite phantom arrays