-
Notifications
You must be signed in to change notification settings - Fork 70
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
All except fix: Option 2 #1038
All except fix: Option 2 #1038
Conversation
f539709
to
ade9f57
Compare
ade9f57
to
b101243
Compare
df.select { name.except { firstNameAccessor } }, | ||
df.select { name.except { firstName and firstName } }, | ||
df.select { name.except { firstNameAccessor and firstNameAccessor } }, | ||
// df.select { name.except(name.firstName and name.firstName) }, // not allowed |
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.
Looks like we need a test for this, but it's not possible in that manner and should be kind of tests for compiler plugin, when it's a String which should be compiled or not
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.
Or could we make assert on that?
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.
yes indeed, that's a good idea for later :)
Fixes #761
NullPointerException
usingexcept
to exclude double nested column #761exceptNew
: Option 1 #1030@ExperimentalExceptCsDsl
and renamesexceptNew
toexcept
@AccessApiOverload
for KProperties and@ExcludeFromSources
for doc interfaces