Should vi.setConfig({ sequence: { concurrent: true } }) work?

[hi-ogawa]

Describe the bug

Docs now mentions it's not supported https://vitest.dev/api/vi.html#vi-setconfig But it's available as typing of vi.setConfig.

vitest/docs/api/vi.md

Lines 977 to 980 in 2a50464

	sequence: {
	hooks: 'stack'
	// supports only "sequence.hooks"
	}

But it might be a regression and possible to make it work again #6653 (comment)

If not, we should update RuntimeConfig to hide it from typing.

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-opxrtz?file=repro.test.ts

(based on tests from #6652)

System Info

(stackblitz)

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @vitest/ui: 2.1.2 => 2.1.2 
    vite: latest => 5.4.8 
    vitest: 2.1.2 => 2.1.2

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sheremet-va]

Conceptually, I don't see why it wouldn't work:

vi.setConfig({ sequence: { concurrent: true } })
describe('suite1') // concurrent
describe('suite2') // concurrent
describe('suite3', { concurrent: false }) // sequential

The question is here, I guess:

describe('suite1', () => {
  vi.setConfig({ sequence: { concurrent: true } })
  describe('suite2') // should it inherit parent suite options or follow global config?
})