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

Allow inline workspace #6913

Closed
4 tasks done
sheremet-va opened this issue Nov 15, 2024 · 0 comments · Fixed by #6923
Closed
4 tasks done

Allow inline workspace #6913

sheremet-va opened this issue Nov 15, 2024 · 0 comments · Fixed by #6923
Labels
p3-significant High priority enhancement (priority)

Comments

@sheremet-va
Copy link
Member

Clear and concise description of the problem

It would be nice to support inline workspace configuration:

export default defineConfig({
  test: {
    workspace: [
      {
        test: { 
          name: 'node', 
          environment: 'node'
        }, 
      },
      {
        test: { 
          name: 'jsdom', 
          environment: 'jsdom'
        }, 
      }
    ]
  }
})

This feature is required for #6912 to make the migration easier.

Suggested solution

Alllow inlined workspace in the main config.

Alternative

No response

Additional context

Some questions:

  1. Should inline workspace override the workspace file? Or should they be merged instead?
  2. Is there a way to reduce the nesting?

Validations

@sheremet-va sheremet-va changed the title Inline workspace Allow inline workspaces to make the migration easier Nov 15, 2024
@sheremet-va sheremet-va changed the title Allow inline workspaces to make the migration easier Allow inline workspaces Nov 15, 2024
@sheremet-va sheremet-va changed the title Allow inline workspaces Allow inline workspace Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p3-significant High priority enhancement (priority)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant