-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Nv 1130 generic error message should point at #2836
Nv 1130 generic error message should point at #2836
Conversation
NV-1130 Generic error message should point at specific missing part
This message here should be more clear in regards to what is missing: CleanShot 2022-11-02 at 23.19.142x.png Created via Raycast |
…-message-should-point-at
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.
Amazing work! Added a feq comments, other than that looks good to me. 🎉
@@ -162,6 +162,8 @@ export function FlowEditor({ | |||
const oldNode = nodes[i + 1] || { position: { x: 0, y: 120 } }; | |||
const newId = (step._id || step.id) as string; | |||
|
|||
await triggerErrors('steps'); |
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.
Why this one is needed here? It triggers the form validation if i understand correctly?
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.
This is to get the meaningful errors before the submit of the form. So we would know what are the errors immediately on adding a node @scopsy
|
||
const { watch } = useFormContext(); | ||
let showErrors = initialErrors; |
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.
This one sounds like a boolean to me, maybe we can rename this to: formErrorsContent
or similar?
What change does this PR introduce?
Show more explicit errors on step node. on update click and on Test workflow.
Why was this change needed?
Other information (Screenshots)
https://www.loom.com/share/dd2fba28845544b48263c64edb1fd432