[turbo.json/ui] add option for task to override global ui setting #9091
Replies: 1 comment 4 replies
-
|
What behavior would you expect to see when running |
Beta Was this translation helpful? Give feedback.
-
|
In this case, I would expect turbo to error due to the mismatch of UI modes. The error message would then also state why it did error. Alternatively, the global UI configuration should be used (although this doesn't really make sense to me?). What do you think of this? |
Beta Was this translation helpful? Give feedback.
-
|
That sounds like a fairly unpleasant experience. If I run valid tasks, I would want them to get their work done. Reading your proposal again, I just realized this line:
Does #8351 seem like it would suit your needs? The proposal there seems much more workable to me. |
Beta Was this translation helpful? Give feedback.
-
|
That sounds like a different approach with pretty much the same result 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
Would you say we could close this discussion in favor of that one, then? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
Non-goals
No response
Background
I really love the TUI, but for some tasks it might make sense to use
streamas a UI setting instead of the TUI.An example would be unit tests in a single package with some interactivity (think Vitest) where in the TUI you would have to hit Enter and then interact with the output.
Adding the option to override the UI mode in specific tasks would allow for more granular use of the individual UI modes based on their use case.
It's not the end of the world if this wouldn't be implemented, but I think it would be nice to have.
Proposal
Allow for a
turbo.jsonlike the following:{ "$schema": "https://turborepo.org/schema.json", "ui": "tui", "tasks": { "start": { "cache": false }, "test.unit": { + "ui": "stream", "cache": true } } }Beta Was this translation helpful? Give feedback.
All reactions