windows-terminal/.github/actions/spelling/patterns
Josh Soref 774f74258f
ci: upgrade to check-spelling v0.0.24 (#18261)
This upgrades to [check-spelling v0.0.24].

A number of GitHub APIs are being turned off shortly, so we need to
upgrade or various uncertain outcomes will occur.

There are some minor bugs that I'm aware of and which I've fixed since
this release (including a couple I discovered while preparing this PR).

There's a new accessibility forbidden pattern:

#### Should be `cannot` (or `can't`)

See https://www.grammarly.com/blog/cannot-or-can-not/
> Don't use `can not` when you mean `cannot`. The only time you're
likely to see `can not` written as separate words is when the word `can`
happens to precede some other phrase that happens to start with `not`.
> `Can't` is a contraction of `cannot`, and it's best suited for
informal writing.
> In formal writing and where contractions are frowned upon, use
`cannot`.
> It is possible to write `can not`, but you generally find it only as
part of some other construction, such as `not only . . . but also.`
- if you encounter such a case, add a pattern for that case to
patterns.txt.
```
\b[Cc]an not\b
```

[check-spelling v0.0.24]: https://github.com/check-spelling/check-spelling/releases/tag/v0.0.24

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
2024-12-04 12:06:31 -06:00
..
README.md Check spelling 0.0.22 (#16127) 2023-12-05 15:40:23 -08:00
patterns.txt ci: upgrade to check-spelling v0.0.24 (#18261) 2024-12-04 12:06:31 -06:00

README.md

The contents of each .txt file in this directory are merged together. Each line is a Perl 5 regular expression. Nothing is guaranteed about the order in which they're merged. -- If this is a problem, please reach out.

Note: order of the contents of these files can matter. Lines from an individual file are handled in file order. Files are selected in alphabetical order.

  • patterns is the main list -- there is nothing particularly special about the file name (beyond the extension which is important).