Skip to content

Let typos accept the renamed Noto Sans font file - #10

Draft
francois-unity wants to merge 1 commit into
unity/a11y-automationfrom
unity/typos-noto-sans
Draft

francois-unity wants to merge 1 commit into
unity/a11y-automationfrom
unity/typos-noto-sans

Conversation

@francois-unity

Copy link
Copy Markdown
Collaborator

Lets typos accept the Noto Sans font file under its new name, so the typos job passes again on PRs into unity/a11y-automation.

Why: upstream gpui-ce#317 (now in this branch) renamed NotoSans[wdth,wght].subset.ttf to NotoSans[wdth-wght].subset.ttf, and typos.toml only ignores the comma spelling. typos then reads wdth, the OpenType width axis tag, as a misspelled “width” in the asset’s file name and in crates/gpui_ce_fonts/src/lib.rs:51, and fails (#7 shows it, job log). The ignore pattern now accepts either separator, because the font’s README still names the comma spelling. Upstream’s typos.toml has the same comma-only pattern.

How to test

  • CI: the typos job passes on this PR.
  • Locally, with typos 1.47.2: typos --config typos.toml reports nothing.

Upstream gpui-ce#317 renamed `NotoSans[wdth,wght].subset.ttf` to
`NotoSans[wdth-wght].subset.ttf`, and `typos.toml` only ignores the
comma spelling. So `typos` reads `wdth`, the OpenType width axis tag,
as a misspelled "width" in the asset’s file name and in
`crates/gpui_ce_fonts/src/lib.rs`, and fails on every PR into
`unity/a11y-automation`. The ignore pattern now accepts either
separator, since the font’s README still names the comma spelling.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant