- πΊπΈUnited States hestenet Portland, OR πΊπΈ
It sounds like we can move this forward incrementally by starting with a core issue and an MR to update the Cspell forbidden words list with an initial pass.
However, there is a tradeoff - Cspell can check everything, but can't do a custom error message to suggest an alternative, phpcs can check only code, but can do custom error messages.
I guess the ideal case would be to somehow hook into the cspell error and offer help text if it exists, maybe in another piece of yaml?
- π¨π¦Canada mgifford Ottawa, Ontario
- π¬π§United Kingdom catch
Moving this to the core queue.
We already added whitelist/blacklist to flagWords after changing those to allow/denylist and similar equivalents in both comments and code - all of which turned out to be good technical changes in their own right.
The only other technical concept that I think we could specifically avoid in core (off the top of my head) is master/slave where we already changed the terminology in the database API over a decade ago. I think we still have help text somewhere that references master/slave which might not be necessary now a lot of projects use replica and similar, but that can also be handle by cspell:ignore for specific cases.