Skip to content

New rule: Normalize string keys

Open

Description

Rule details

Normalize string keys

What type of rule is this?

Suggests an alternate way of doing something

Example code

Per https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/normalize , there are examples of unicode that are similar in character. Generally this could mean that there is a key mismatch on 2 apparently similar strings. Suggesting using a normalized form to avoid this potential issue would be good so that the following 2 object don't have mismatched keys:

{
  "Amélie": 1
}
{
  "Amélie": 2
}

There are valid use cases for these key mismatches, but they are generally very specific in scope.

Participation

  • I am willing to submit a pull request to implement this rule.

Additional comments

Similar mismatches or deception such as using Bidi mixing / zero width characters etc. are potentially in the same vein but likely would be a different scope since those have associated CVEs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions