fix: Resolve Panics In Code Gen When Schema Fields Use DefaultFunc #71
Conversation
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
lillialjackson
approved these changes
Mar 10, 2025
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.
Description
Resolve Panics In Code Gen When Schema Fields Use DefaultFunc
Resolves #70
Motivation and Context
Turns out some fields in ent have both a
Defaultmethod and aDefaultFuncmethod which serve similar but still different purposes, this accounts for the code gen related to bothHow Has This Been Tested?
Updated schema and generated, unit tests pass without change required
Screenshots (if appropriate):
N/A
Types of changes
Checklist: