fix(typescript): propagate tags to validate_options#3260
fix(typescript): propagate tags to validate_options#3260alexeagle merged 2 commits intobazel-contrib:stablefrom
Conversation
alexeagle
left a comment
There was a problem hiding this comment.
Thanks!
Do you think we might want testonly and visibility to be propagated as well? Just thinking to be consistent with https://github.com/bazelbuild/rules_nodejs/blob/5.x/packages/typescript/index.bzl#L507-L511
Seems reasonable. The target is named with a leading underscore ( |
|
@alexeagle I moved |
|
buildifier failed - I'd suggest running |
a499713 to
afc5937
Compare
fixed & force pushed the last commit (not sure what the convention for this repo is in terms of the structured commit messages and trivial typo fixes like that...) |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #3259
What is the new behavior?
Tags are propagated to the validate_options rule
Does this PR introduce a breaking change?
Strictly, the answer here might be yes, particularly if someone was doing something very esoteric with custom tags and relying on the fact that propagation to this rule was not happening, but this seems extremely unlikely.
Other information