Define a semantics-preserving Bazelrc formatting contract #23

New issue

Closed

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

barrettruth commented

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

Owner

Original issue: source #24
Original author: barrettruth
Original date: 2026-08-31T06:08:08Z

Parent: #6

Decide whether a useful formatter can preserve the upstream Bazel 8.7 byte grammar exactly. Specify treatment of continuations, quote-fragment concatenation, escapes, mid-token comments, CRLF, blank lines, and comment runs before implementation.

The source-derived grammar corpus is authoritative. If the only safe formatter is too narrow or produces unstable edits, record formatting as an intentional non-feature rather than inventing a canonical style Bazel does not define.

> Original issue: source #24 > Original author: `barrettruth` > Original date: 2026-08-31T06:08:08Z Parent: #6 Decide whether a useful formatter can preserve the upstream Bazel 8.7 byte grammar exactly. Specify treatment of continuations, quote-fragment concatenation, escapes, mid-token comments, CRLF, blank lines, and comment runs before implementation. The source-derived grammar corpus is authoritative. If the only safe formatter is too narrow or produces unstable edits, record formatting as an intentional non-feature rather than inventing a canonical style Bazel does not define.

barrettruth added this to the v0.2.0 milestone

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

barrettruth

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