-
Notifications
You must be signed in to change notification settings - Fork 205
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
add silent_annotations option to da_scala bazel functions #7668
Conversation
CHANGELOG_BEGIN CHANGELOG_END
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.
Nice, thank you!
name = "", | ||
scalacopts = [], | ||
plugins = [], | ||
generated_srcs = [], # hiding from the underlying rule |
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.
My hiding
you mean we don’t pass it along? Do you know why we even have this field then?
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.
It's there to make sure it doesn't end up in kwargs
.
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.
Nice, thank you
During #6907 it became obvious that a simpler way to declare that a build rule wished to enable
@silent
would be very nice, but that PR was already quite large enough. #7661's effective requirement of sed-based build file editing clarified that we should resolve this boilerplate.So here it is: add
silent_annotations = True
to your Scala build if you want access to the@silent
annotation, delete it if you don't need it anymore.As a (desired) side effect of abstracting this, every use of silencer also acquires the
checkUnused
option in this PR to ensure that we clean up stray@silent
s.Pull Request Checklist
CHANGELOG_BEGIN
andCHANGELOG_END
tagsNOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with
/AzurePipelines run
totrigger the build.