You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if isScalar is required here. If I understand it correctly, the purpose for checking isScaler is to make sure there is no Merger applicable. However, Merger is designed for src to merge dst, and when src is nil, there is no way for it to do a custom merge.
I think it's safe to remove the isScaler check, and remove dst regardless.
ashi009
added a commit
to ashi009/bazel-gazelle
that referenced
this issue
Dec 10, 2024
What version of gazelle are you using?
0.37.0
What version of rules_go are you using?
0.49.0
What version of Bazel are you using?
7.2.1
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
macOS 15.1 aarch64
What did you do?
I generated some empty rules to remove existing rules in BUILD files:
The kind definition has:
and the current build file has:
What did you expect to see?
the "test" target gets removed.
What did you see instead?
and the target is untouched after the run.
This is because when merging the attrs, if the dst is not a scalar, it can't be removed.
bazel-gazelle/rule/merge.go
Line 105 in 2898dda
The text was updated successfully, but these errors were encountered: