-
Notifications
You must be signed in to change notification settings - Fork 4.5k
incompatible_remove_rule_name_parameter #16301
Copy link
Copy link
Closed
Labels
P1I'll work on this now. (Assignee required)I'll work on this now. (Assignee required)breaking-change-6.0Incompatible flags to be flipped in Bazel 6.0Incompatible flags to be flipped in Bazel 6.0incompatible-changeIncompatible/breaking changeIncompatible/breaking changemigration-readyIncompatible flag is ready for migration with Bazel rolling releases or Bazel@last_greenIncompatible flag is ready for migration with Bazel rolling releases or Bazel@last_green
Milestone
Metadata
Metadata
Assignees
Labels
P1I'll work on this now. (Assignee required)I'll work on this now. (Assignee required)breaking-change-6.0Incompatible flags to be flipped in Bazel 6.0Incompatible flags to be flipped in Bazel 6.0incompatible-changeIncompatible/breaking changeIncompatible/breaking changemigration-readyIncompatible flag is ready for migration with Bazel rolling releases or Bazel@last_greenIncompatible flag is ready for migration with Bazel rolling releases or Bazel@last_green
There are semantic problems with using
rule(name=..., ...)instead of usingname = rule(...)on the top-level, because there can be multiple rules with the same name exported from a singlebzlfile.We decided to remove
nameparameter from therulecall.Expected timeline: