This was added in #82 but it didn't account for the "NextJS" typo which is quite common

(should be "Next.js" as seen on https://nextjs.org)

Closes #27

Allows a user to provide their own .json file to be appended onto the default dictionary via the --append option e.g. npx case-police --append my-dictionary.json --fix

npm should always be lowercase, no matter where. See npm docs (emphasis mine):

npm is the world's largest software registry. Open source developers from every continent use npm to share and borrow packages, and many organizations use npm to manage private development as well.

Describe the bug

case-police flags NATs as incorrect, I'm trying to describe the plural of a Network Address Translator

Reproduction

Lint a file with NATs in it

System Info

System:
    OS: macOS 12.5
    CPU: (10) arm64 Apple M1 Max
    Memory: 14.20 GB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.7.0 - ~/.volta/tools/image/node/18.7.0/bin/node
    Yarn: 1.22.18 - ~/.volta/tools/image/yarn/1.22.18/bin/yarn
    npm: 8.17.0 - ~/.volta/tools/image/npm/8.17.0/bin/npm
  Browsers:
    Firefox: 103.0.2
    Safari: 15.6

Used Package Manager

npm

Validations

• [X] Follow our Code of Conduct
• [X] Read the Contributing Guide.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• [X] The provided reproduction is a minimal reproducible of the bug.

Describe the bug

RESPONSE=$(curl -sSL -H "${AUTH_HEADER}" -H "${HEADER}" --user "${GITHUB_ACTOR}" -X GET --data "${DATA}" ${PULLS_URL}) case-police tells me that sSL should be SSL though this is a curl shorthand rather than a word

Reproduction

https://stackblitz.com/edit/vitejs-vite-5bjczq?file=run.sh

System Info

System:
    OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (16) x64 AMD EPYC 7B13
    Memory: 19.95 GB / 62.81 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.16.0/bin/yarn
    npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm

Used Package Manager

yarn

Validations

• [X] Follow our Code of Conduct
• [X] Read the Contributing Guide.
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• [X] The provided reproduction is a minimal reproducible of the bug.

Please read the Contributions Guide before making Pull Requests.

Hi @antfu ! 👋 Thanks for this project, really cool!

Quick PR to add webpack, since I see this commonly cased as Webpack.

Thinking about this rule:

• Since case-police will only fix words that have both lowercase and uppercase letters, it WON'T convert java to Java. If correct form is a single capitalized word, there is no need to add it to the dictionary.

, is that means if I have a entry:

{
  // ...
  "eslint": "ESLint"
  // ...
}

, case-police will not change eslint to ESLint?

But eslint have already in dict.json, is this guidelines express with confusing?

Please read the Contributions Guide before making Pull Requests.

PR #120 breaks some languages such as Japanese and Chinese. For example: GithubのVScode Github的VScode Github：

containsUTF8 will return true because it takes Githubの, のVScode,Github的 ,的VScode and Github： as a whole respectively, so the Github and VScode won't be corrected. UTF-8 support should be implemented in another way.

Previously we call it Nebula Graph, until this week, it’s rebranded as NebulaGraph, yes, we could ~~finally be a thing in case police then~~!

Update: it turned out that the case-police supported space separated phrase before.

For example, the following file:

Romania (România)

Cause this output:

 Case  Police  v0.3.0

1475 files found for checking

Rom → ROM         ./file