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

Update eslint-plugin-import #164

Merged
merged 1 commit into from
Aug 31, 2023
Merged

Update eslint-plugin-import #164

merged 1 commit into from
Aug 31, 2023

Conversation

yndajas
Copy link
Contributor

@yndajas yndajas commented Aug 31, 2023

Context

eslint-plugin-import introduced a breaking change to import/order where single nested groups were effectively denested. I (hopefully) fixed this in import-js/eslint-plugin-import#2854, which has been released

Changes in this PR

  • Update eslint-plugin-import and revert complication of rule

Release checklist

Release process documentation

As part of our continuous deployment strategy we must ensure that this work is
ready to be released once merged.

Pre-merge

  • There are changes required to the Accredited Programmes API for this change to work...
    • ... and they have been released to production already

Post-merge

  • This adds, extends or meaningfully modifies a feature...
  • This makes new expectations of the API...
    • ... and I have notified the API developer(s) of changes to the contract tests (Pact), or the API is already compliant
  • Manually approve release to preprod
  • Manually approve release to prod

@yndajas yndajas force-pushed the update-eslint-plugin-import branch from ff63b5e to 79badbf Compare August 31, 2023 15:46
2.28.0 introduced a breaking change to `import/order` where the order
of nested groups (whose purpose is to define different types of imports
that are of equivalent rank) started to matter: a single nested group
would be treated as though it wasn't nested

We [got around this][1] by adding a second nested group with most if
not all of the other import types we use

It looks like #141
brought us back to 2.27.5. If we go back to 2.28.0 now and revert to
the simpler config, for some reason the ESLint errors don't reappear

In any case, I submitted a [bug fix][2] in eslint-plugin-import 💅
This was released in 2.28.1, so we should upgrade, hopefully preventing
an unexpected return to confusing errors

[1]: ab5a73e
[2]: import-js/eslint-plugin-import#2854
@yndajas yndajas force-pushed the update-eslint-plugin-import branch from 79badbf to 47bf31b Compare August 31, 2023 16:03
Copy link
Contributor

@bell-pa bell-pa left a comment

Choose a reason for hiding this comment

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

LGTM

@yndajas yndajas merged commit 38a785f into main Aug 31, 2023
3 checks passed
@yndajas yndajas deleted the update-eslint-plugin-import branch August 31, 2023 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants