Bazelrc 8.7 authoring #6

New issue

Closed

opened 2026-09-21 01:14:14 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-09-21 01:14:14 +00:00

Owner

Original issue: source #6
Original author: barrettruth
Original date: 2026-08-26T07:00:54Z

The v0.2.0 epic for a coherent Bazelrc authoring surface. The normative language contract is upstream Bazel 8.7.0; native flag intelligence requires an exact numeric-8.7 catalog from the configured executable.

Already shipped:

native byte grammar and physical source ranges;
workspace-root import graph and import/configuration navigation;
command/configuration/native-flag completion;
native flag hover and conservative diagnostics;
semantic tokens, folding, selection ranges, and document links.

The attached sub-issue tree is topological: configuration identity and expansion edges precede graph analysis, reference features precede rename, published path candidates precede import completion, and a formatting contract precedes any formatter.

Not part of v0.2.0:

vendor-build-label language semantics;
system, home, or explicit rc discovery;
full effective-command-line reconstruction;
arbitrary option-converter emulation;
any Bazel 9 behavior.

Requests continue to use one immutable document/index/configuration/catalog snapshot and perform no filesystem or Bazel work.

> Original issue: source #6 > Original author: `barrettruth` > Original date: 2026-08-26T07:00:54Z The v0.2.0 epic for a coherent Bazelrc authoring surface. The normative language contract is upstream Bazel 8.7.0; native flag intelligence requires an exact numeric-8.7 catalog from the configured executable. Already shipped: - native byte grammar and physical source ranges; - workspace-root import graph and import/configuration navigation; - command/configuration/native-flag completion; - native flag hover and conservative diagnostics; - semantic tokens, folding, selection ranges, and document links. The attached sub-issue tree is topological: configuration identity and expansion edges precede graph analysis, reference features precede rename, published path candidates precede import completion, and a formatting contract precedes any formatter. Not part of v0.2.0: - vendor-build-label language semantics; - system, home, or explicit rc discovery; - full effective-command-line reconstruction; - arbitrary option-converter emulation; - any Bazel 9 behavior. Requests continue to use one immutable document/index/configuration/catalog snapshot and perform no filesystem or Bazel work.

barrettruth added this to the v0.2.0 milestone

2026-09-21 01:14:14 +00:00

barrettruth

2026-09-21 01:14:14 +00:00