You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Overall, no need to be strict here about American vs British English or including variable names in a dict vs ignoring them each time they come up. Instead, let's focus on integrating an automated check that works so devs can quickly scan files and publish them with confidence.
CI fails if words are marked as spelled incorrectly
Contributors can easily update the list of known words
Contributors can easily ignore entire files if they want to
Contributors can easily identify words marked as spelled incorrectly via their IDE as a standard info squiggle (similar to warnings)
Words that can probably be changed:
unittests -> unit tests
coredev -> core dev
toolcaps -> tool caps?
crossview -> cross-view
Future considerations:
style guide entry on American vs British vs "other" English?
The text was updated successfully, but these errors were encountered:
Overall, no need to be strict here about American vs British English or including variable names in a dict vs ignoring them each time they come up. Instead, let's focus on integrating an automated check that works so devs can quickly scan files and publish them with confidence.
Words that can probably be changed:
Future considerations:
The text was updated successfully, but these errors were encountered: