-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Payload not updated when using request.error filter #17002
Labels
Comments
Linear: ENG-378 |
9 tasks
This should have either been an |
From what I gather, this is due to a small bug in the error-handler, corrected by #17003. It works for my use cases, but maybe I miss some side effects |
rijkvanzanten
added a commit
that referenced
this issue
Apr 11, 2023
rijkvanzanten
added a commit
that referenced
this issue
Apr 11, 2023
hanneskuettner
pushed a commit
to hanneskuettner/directus
that referenced
this issue
Apr 18, 2023
meditadvisors
pushed a commit
to ciso360ai/directus-mod
that referenced
this issue
May 13, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the Bug
When updating the payload in a flow or an extension using the
request.error
filter, the changes are discardedTo Reproduce
The following script should prevent fields with a
must be [null]
validation to display an error message to the user:But the error message is displayed to the user.
Errors Shown
No response
What version of Directus are you using?
9.22.1
What version of Node.js are you using?
16.16.0
What database are you using?
SQLite 3.40.0
What browser are you using?
Safari
How are you deploying Directus?
running locally
The text was updated successfully, but these errors were encountered: