-
-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
merge dev to main (v1.10.1) #1099
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -105,7 +105,7 @@ plugin policy { | |
|
||
plugin zod { | ||
provider = '@core/zod' | ||
// preserveTsFiles = true | ||
preserveTsFiles = true | ||
modelOnly = ${!options.fullZod} | ||
} | ||
`; | ||
Comment on lines
105
to
111
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The use of
The use of
Also applies to: 75-75 |
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The adjustments in the
binary
method to handle binary expressions based onExpressionContext.ValidationRule
andisDataModelFieldReference
are well thought out. These changes ensure that binary operations involving undefined fields in a validation context are treated as booleantrue
. This consistent approach to handling undefined values in validation contexts across different expression types is commendable. However, it's important to ensure comprehensive testing around these changes to validate their correctness in various scenarios.Ensure comprehensive testing is conducted around the changes in the
binary
method to validate their correctness across various scenarios, particularly focusing on edge cases involving undefined values in validation contexts.