-
Notifications
You must be signed in to change notification settings - Fork 83
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
Attempting to save a product without a required field should identify the field that failed #114
Comments
And open and focus on the first error input... |
So we've written about ten issues for this same problem now and can't seem to get this solved. So I think the requirements here are: If a new product fail validation from Simple Schema it should:
Things it should not do
|
@zenweasel That UX feels right. Thanks for detailing that. |
I'd like to add that under no (normal) circumstance should saving a Product cause the server to throw an error because of invalid schema.
I'm still seeing this error when attempting to publish a product without a title. We should be validating on the client before sending to the server and not relying on the server to respond with an error before informing the user that the fields are invalid. |
Right, I think I covered that in point one, but it stands to be said again. This is webdev 101, validate on the client before validating on the server. If we are still getting server errors, this ticket is not complete. |
Referenced UI is gone |
When trying to save a product that doesn't have a title, I receive a toast alert letting me know that the title is required, but the field does not get highlighted, nor does the panel open to the product edit panel when I try to save a product without a title.
The UI should identify the field that failed and open the action view panel to the correct section as it does when attempting to save an invalid field in a variant.
Server error is caused as well. We should attempt to catch this invalid product before sending it to the server.
The text was updated successfully, but these errors were encountered: