Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more words to awesome/spell-check #36

Open
6 of 8 tasks
transitive-bullshit opened this issue Aug 16, 2018 · 6 comments · Fixed by #40
Open
6 of 8 tasks

Add more words to awesome/spell-check #36

transitive-bullshit opened this issue Aug 16, 2018 · 6 comments · Fixed by #40

Comments

@transitive-bullshit
Copy link
Collaborator

transitive-bullshit commented Aug 16, 2018

I'm going to track the master list of words we've officially decided to spell check in this first comment. As we agree on additional words to add to the spell check list, I'll update this list accordingly.

Done:

  • Node.js
  • Stack Overflow
  • JavaScript
  • macOS
  • YouTube
  • GitHub

Todo:

  • FFmpeg
  • Open Source
@sindresorhus
Copy link
Owner

sindresorhus commented Aug 16, 2018

  • FFmpeg
  • Youtube => YouTube
  • Github => GitHub

@transitive-bullshit transitive-bullshit changed the title Add macOS to awesome/spell-check Add more words to awesome/spell-check Aug 16, 2018
@itaisteinherz
Copy link
Contributor

Regarding #40 and FFmpeg, note that awesome-lint currently lints just text nodes (more info about this here and here):

module.exports = rule('remark-lint:awesome/spell-check', (ast, file) => {
visit(ast, 'text', node => {

Which means that even if this is the markdown file:

This is a document about `ffmpeg`.

ffmpeg wouldn't be linted. To solve this we could add more regexes which match ffmpeg (case sensitive) as a text node and ffmpeg (case insensitive) as a code node and assert that the match is ffmpeg as a code node (this requires visiting every code node in the AST, in addition to the text nodes).

@transitive-bullshit
Copy link
Collaborator Author

I really appreciate you helping out with this @itaisteinherz.

Your logic makes sense. I just wasn't sure without manually testing whether inline code snippets contained text nodes as children in which case ffmpeg couldn't necessarily be differentiated from a text node "ffmpeg".

With that being said, given that you've added the relevant unit test to cover this case, I think my reservations are handled, though I'll let @sindresorhus make the final call on this scenario.

@itaisteinherz
Copy link
Contributor

itaisteinherz commented Sep 3, 2018

Some more ideas for terms we could spell-check:

  • npm
  • GitLab
  • AVA (not sure what's the preferred case here - AVA or ava)
  • XO (same comment as above)
  • Linux (since we've already added one OS; we probably shouldn't add Windows for now, as it's a widely used word in contexts other than the OS, and it would complicate things)
  • iOS, watchOS, tvOS (to accompany macOS)
  • Docker
  • DB names: MySQL, MongoDB, Neo4j, etc.
  • Popular file formats - PNG, PDF, etc.
  • Cryptocurrencies - Bitcoin, Ethereum, etc.

We could also add some more language names (i.e. Swift, Python, etc.), since we already have Node.js.

There are a lot of words and terms we could spell-check, and so I think we should decide on some guidelines as to which words we spell-check and which words we don't.

@transitive-bullshit
Copy link
Collaborator Author

There are a lot of words and terms we could spell-check, and so I think we should decide on some guidelines as to which words we spell-check and which words we don't.

Agreed. imho I'd rather keep the list very small and targeted for now until we figure out what to do with #39 since I really want to be careful about the possibility of adding false positives before an initial integration with the greater awesome list community.

@sindresorhus
Copy link
Owner

@itaisteinherz All your suggestions look good to me. For AVA and XO, it's all uppercase.

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 a pull request may close this issue.

3 participants