You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, migrate-config just takes the evaluated version of a .eslintrc.js file and converts that. While that works fine for mostly static .eslintrc.js files, it's not a good solution for complicated ones.
What do you think is the correct solution?
Ideally, we'd be able to do some code modifications via something like jscodeshift to update a .eslintrc.js file. This would likely be a different code path than for static config files.
Participation
I am willing to submit a pull request for this change.
Additional comments
I don't have the bandwidth to take this on, so looking for a volunteer to investigate this.
The text was updated successfully, but these errors were encountered:
Which packages would you like to change?
@eslint/compat
@eslint/config-array
@eslint/migrate-config
@eslint/object-schema
What problem do you want to solve?
Right now,
migrate-config
just takes the evaluated version of a.eslintrc.js
file and converts that. While that works fine for mostly static.eslintrc.js
files, it's not a good solution for complicated ones.What do you think is the correct solution?
Ideally, we'd be able to do some code modifications via something like jscodeshift to update a
.eslintrc.js
file. This would likely be a different code path than for static config files.Participation
Additional comments
I don't have the bandwidth to take this on, so looking for a volunteer to investigate this.
The text was updated successfully, but these errors were encountered: