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

Regression in import/order rule after v2.26 #3034

Closed
burt202 opened this issue Aug 11, 2024 · 1 comment
Closed

Regression in import/order rule after v2.26 #3034

burt202 opened this issue Aug 11, 2024 · 1 comment

Comments

@burt202
Copy link

burt202 commented Aug 11, 2024

Related to #2909

Hi, im currently still stuck on v2.26 because a regression made in v2.27 which incorrectly suggests the wrong order for my config. I have cloned the repo and written a test which works in 2.26 but fails in the latest version which may help:

test({
  code: `
  import express from "express"
  import server from "http"

  import logger from "../logger"
  import something from "../utils"
  import {Config, Route, Server} from "./types"
  `,
  options: [
    {
      'newlines-between': 'always',
      groups: [
        ['builtin', 'external'],
        ['parent', 'sibling', 'index'],
      ],
      alphabetize: {
        order: 'asc',
      },
    },
  ],
}),

This has obviously been an issue since Oct 2023 and i know there have been others that have raised similar issues too. I just wondered how to progress.

  • Is my config wrong and need updating for versions beyond 2.26 to enforce the same order?
  • Is this an agreed regression and need fixing, maybe i could help here?

Cheers!

@ljharb
Copy link
Member

ljharb commented Aug 12, 2024

I think this is a duplicate of #2722.

Help is appreciated there.

@ljharb ljharb closed this as not planned Won't fix, can't repro, duplicate, stale Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants