This repository has been archived by the owner on Aug 31, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 659
no-dupe-keys
#3364
Labels
A-Linter
Area: linter
good first issue
Good for newcomers
I-Easy
Implementation: easy task, usually a good fit for new contributors
S-Planned
Status: planned by the team, but not in the short term
Comments
ematipico
changed the title
Oct 7, 2022
no-dupe-keys
https://eslint.org/docs/rules/no-dupe-keysno-dupe-keys
ematipico
added
A-Linter
Area: linter
I-Easy
Implementation: easy task, usually a good fit for new contributors
hacktoberfest
Issues for hacktoberfest
good first issue
Good for newcomers
labels
Oct 7, 2022
I take care of that |
I assigned the issue to you @MoskalykA ! |
This issue is stale because it has been open 14 days with no activity. |
ematipico
added
S-Planned
Status: planned by the team, but not in the short term
and removed
hacktoberfest
Issues for hacktoberfest
labels
Nov 2, 2022
Since this appears to be inactive, I'm trying this one out to write my first lint rule, let's see how they are written in Rome 😄 |
Go for it! |
MichaReiser
pushed a commit
that referenced
this issue
Nov 14, 2022
Co-authored-by: Micha Reiser <[email protected]> Resolves #3364
nhedger
pushed a commit
to biomejs/biome-vscode
that referenced
this issue
Sep 21, 2023
Co-authored-by: Micha Reiser <[email protected]> Resolves rome/tools#3364
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
A-Linter
Area: linter
good first issue
Good for newcomers
I-Easy
Implementation: easy task, usually a good fit for new contributors
S-Planned
Status: planned by the team, but not in the short term
https://eslint.org/docs/rules/no-dupe-keys
The text was updated successfully, but these errors were encountered: