- Notifications
You must be signed in to change notification settings - Fork1.1k
fix: use default preset when creating a workspace for task#18623
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
c943a05 to2ab771cCompare
dannykopping left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Looks good but don't we need a test?
BrunoQuaresma commentedJun 27, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
It would be great, but in the way we have the fetch calls structured/abstracted right now, it makes testing this quite painful. Since this is going to be a BE endpoint any time soon, I would not invest time on refactoring to make it more testable. Wdyt@code-asher ? |
6d305df intomainUh oh!
There was an error while loading.Please reload this page.
BrunoQuaresma commentedJun 27, 2025
It is merged, but I'm open to add tests in case we find out a good solution for it. |
dannykopping commentedJun 27, 2025
Not even a storybook? |
BrunoQuaresma commentedJun 27, 2025
It already has a storybook 🤔 |
dannykopping commentedJun 27, 2025
For tasks? |
BrunoQuaresma commentedJun 27, 2025
dannykopping commentedJun 28, 2025
I don't see any mention of presets in that test; am I missing something? |
No description provided.