Skip to content
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.

no-dupe-keys #3364

Closed
Tracked by #3358
ematipico opened this issue Oct 7, 2022 · 5 comments · Fixed by #3562
Closed
Tracked by #3358

no-dupe-keys #3364

ematipico opened this issue Oct 7, 2022 · 5 comments · Fixed by #3562
Assignees
@jeysal
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
Copy link
Contributor

ematipico commented Oct 7, 2022 •
edited
Loading

https://eslint.org/docs/rules/no-dupe-keys
@ematipico ematipico mentioned this issue Oct 7, 2022
Closed
11 tasks
@ematipico ematipico changed the title no-dupe-keys https://eslint.org/docs/rules/no-dupe-keys no-dupe-keys Oct 7, 2022
@ematipico ematipico added this to the 10.0.0 milestone Oct 7, 2022
@ematipico 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
@MoskalykA
Copy link

I take care of that

@ematipico
Copy link
Contributor Author

I take care of that

I assigned the issue to you @MoskalykA !

@github-actions
Copy link

This issue is stale because it has been open 14 days with no activity.

@ematipico 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
@ematipico ematipico modified the milestones: 10.0.0, 10.1.0 Nov 2, 2022
@github-actions github-actions bot removed the S-Stale label Nov 3, 2022
@jeysal
Copy link
Contributor

jeysal commented Nov 3, 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 😄

@MichaReiser MichaReiser assigned jeysal and unassigned MoskalykA Nov 3, 2022
@MichaReiser
Copy link
Contributor

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!

@jeysal jeysal mentioned this issue Nov 4, 2022
Merged
MichaReiser pushed a commit that referenced this issue Nov 14, 2022
@jeysal
feat(rome_js_analyze): lint/correctness/noDupeKeys (#3562)
7082c83 
Co-authored-by: Micha Reiser <[email protected]>
Resolves #3364
@jeysal jeysal mentioned this issue Nov 14, 2022
Closed
nhedger pushed a commit to biomejs/biome-vscode that referenced this issue Sep 21, 2023
@jeysal
feat(rome_js_analyze): lint/correctness/noDupeKeys (#3562)
d996b00 
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.
Assignees

@jeysal jeysal

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
Projects
Rome 2022
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(rome_js_analyze): lint/correctness/noDupeKeys jeysal/rometools
4 participants
@ematipico @MichaReiser @jeysal @MoskalykA