Open robdekort opened 9 months ago
I've taken a look into this and while you can get rid of the precognitive error by sending over the file name instead of a file object, that then causes issues when you actually submit the form due to it not being a file object.
I wonder if we just filter out validation on asset fields in precognitive requests?
Re-opening since the linked PR doesn't actually fix the issue reported here (the messages not being cleared after a successful submission), it simply prevents validation from being done on asset fields before the form is submitted.
Bug description
When you trigger an asset field error in a form using Precognition, it doesn't get cleared. Jason and I just witnessed this. He knows more about what's actually going on. This could be a Precognition issue instead of a Statamic one.
How to reproduce
The asset field error remains. This is probably easiest to test in Peak as that shows the remaining errors visually on screen already.
Logs
No response
Environment
Installation
Starter Kit using via CLI
Antlers Parser
None
Additional details
No response