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
Manually input design options outside range #6531
base: develop
Are you sure you want to change the base?
Manually input design options outside range #6531
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@VSinerva is attempting to deploy a commit to the freesewing Team on Vercel. A member of the Team first needs to authorize it. |
I think this should be level 4 for consistency with how the user experience setting is used elsewhere. Per the documentation, there is no feature difference between level 4 and 5; the only difference is that on level 5 " For me, I'm not confident enough in FreeSewing to go without any warnings at all, but there are definitely situations where I'd want to manually input options outside the recommended range. |
Based on the documentation for UX levels, I agree. Since Edit by Hand is only available at or above level 4 anyway, I'm gonna update this PR to reflect that. Basically, edit by hand would always allow values outside the given range, but at level 4 it would ask for confirmation, while skipping that at level 5 |
This is a proposed way to close #6335
The idea is to only allow this at UX level 5, and only through "Edit settings by hand". This helps keep it the niche feature it should be, and avoids errors being generated from typos etc. in the live "Draft" view. (These came up as ideas in the discussion linked above)
All errors are still shown as before. The only difference is that at UX 5, if all errors are
RangeError
inoptions
, the settings will be saved regardless. I believe this strikes a balance of not letting inexperienced (or experienced) users make mistakes during their normal workflow, while still giving experienced users increased control when explicitly asked for.There were concerns raised in the discussion of the issue about this feature cluttering automatically generated bug reports with errors. However, I don't think that should be a deal breaker for this feature, because experienced users are already using and saving patterns with parameters out-of-range (by editing the URL). This would still be a 'hidden' niche option, so it's unlikely IMO to see much more usage than the URL-trick already does.
I'm of course open to feedback on the implementation, or on if this should be implemented at all :)