-
Notifications
You must be signed in to change notification settings - Fork 52
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
WIP: Shell dry-run validation with thickness arg #5118
base: main
Are you sure you want to change the base?
WIP: Shell dry-run validation with thickness arg #5118
Conversation
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
1 similar comment
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5118 +/- ##
=======================================
Coverage 85.95% 85.95%
=======================================
Files 90 90
Lines 32912 32912
=======================================
Hits 28291 28291
Misses 4621 4621
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…ions-and-extra-arguments
Yeah this is a good idea within the command bar. Since the user provides these values step by step, it makes sense to help them from shooting themselves in their foot. |
…ions-and-extra-arguments
@nadr0 I was playing with this today. Moves the shell validation to the last argument (thickness) so we can run it on provided selections and thickness. Maybe this workflow could become the default one for the review stage of the command bar process. Or evolve into something else. But I figured this wasn't the only command that it could be useful for. Let me know if you have any thoughts