-
Notifications
You must be signed in to change notification settings - Fork 191
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
Feat: Support top level properties in model_defaults #3696
Conversation
dce784a
to
1154b8e
Compare
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.
LGTM, just one comment.
session_properties[k] = exp.Literal.string(k).eq(v) | ||
if k not in properties: | ||
properties[k] = exp.Literal.string(k).eq(v) | ||
elif properties[k].expression.sql().lower() in {"none", "null"}: |
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.
Is matching null
here safe? Can that be an actual property value?
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.
This is to match for python models properties where None
will be null
here
1154b8e
to
96187e0
Compare
This update extends the support for top-level properties to be enabled project wide, fixes: #3599
Don't know if it makes sense to include more, as the others seem quite model-specific, but I’m happy to add them if anyone feels they’re necessary.