-
Notifications
You must be signed in to change notification settings - Fork 180
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 expand_template rule #330
Conversation
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.
Overall, looks reasonable; but please add a test for the rule.
@brandjon @tetromino Can you review it again, please? I need |
Hey @Vertexwahn if you can't get a response here, we'd love to have your contribution in https://github.com/aspect-build/bazel-lib instead! |
@alexeagle If this gets not merged I will open up a PR on bazel-lib the next days. |
@tetromino Sorry to ping you again - but you reviewed the PR already in the past, I applied several changes (added tests, etc). Can you please review again? |
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 apologies for the delayed review!
Tests look good; what remains is docs.
Please add a bzl_library
entry for expand_template
to rules/BUILD.
Please add a stardoc_with_diff_test
target in docs/BUILD which uses that bzl_library.
Then use bazel run //docs:update
to create the expand_template_doc.md file, and add a link to the doc in README.md
Add a basic expand_template rule to support trivial search and replace use cases.
@tetromino I addressed all your comments. Looking forward to a merge ;) |
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 good. Thank you, and again, sorry for delayed review!
Followup to bazelbuild#330: remove the wrapper macro and export the rule directly; the macro does not serve any useful function. As a side effect, this fixes the inability to set tags etc., since the macro did not support **kwargs.
Followup to #330: remove the wrapper macro and export the rule directly; the macro does not serve any useful function. As a side effect, this fixes the inability to set tags etc., since the macro did not support **kwargs.
Resolves: #191
An example of how this can be usefull can be found here: https://github.com/catchorg/Catch2/pull/2387/files
Could be also helpfull here: https://github.com/AcademySoftwareFoundation/openexr/blob/8587f4eed1d396a9c545d59e7b231d9d4b2cd8ef/BUILD.bazel#L21