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

Chore: Removed lodash.merge #14931

Closed
wants to merge 2 commits into from
Closed

Chore: Removed lodash.merge #14931

wants to merge 2 commits into from

Conversation

jimmywarting
Copy link

Prerequisites checklist

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain:

Addresses part of #14098. Removes lodash from the project

@eslint-github-bot eslint-github-bot bot added the triage An ESLint team member will look at this issue soon label Aug 14, 2021
Copy link
Contributor

@snitin315 snitin315 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you rebase and fix conflicts?

@nzakas
Copy link
Member

nzakas commented Aug 17, 2021

@jimmywarting you have linting and testing errors. Can you please take a look? (You can try things out locally by running npm run lint and npm test to make sure things are fixed.)

@mdjermanovic mdjermanovic added chore This change is not user-facing evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion and removed triage An ESLint team member will look at this issue soon labels Aug 19, 2021
@@ -45,6 +45,7 @@ const DEFAULT_ECMA_VERSION = 5;
const commentParser = new ConfigCommentParser();
const DEFAULT_ERROR_LOC = { start: { line: 1, column: 0 }, end: { line: 1, column: 1 } };
const parserSymbol = Symbol.for("eslint.RuleTester.parser");
const merge = Object.assign;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can't replace here lodash.merge with Object.assign , because merge() is used to merge parserOptions, which should be deeply merged. I added a test case that would fail with Object.assign in #14948.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Guess we can close this PR then cuz Object.assign don't cut it...

@eslint-github-bot eslint-github-bot bot locked and limited conversation to collaborators Feb 16, 2022
@eslint-github-bot eslint-github-bot bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Feb 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion chore This change is not user-facing evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants