Skip to content
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

setErrors fails without any response if second parameter is array. #1248

Closed
dl-ias opened this issue Mar 8, 2024 · 3 comments
Closed

setErrors fails without any response if second parameter is array. #1248

dl-ias opened this issue Mar 8, 2024 · 3 comments
Labels
🐛 bug-report Bug is reported, but not verified by team ⛑ Needs triage The issue has not yet been examined by the FormKit team.

Comments

@dl-ias dl-ias added ⛑ Needs triage The issue has not yet been examined by the FormKit team. 🐛 bug-report Bug is reported, but not verified by team labels Mar 8, 2024
@justin-schroeder
Copy link
Member

Perhaps we need to document this better, but the second argument must be an object of { nodeAddress: [errors] }:

https://formkit.com/inputs/form#using-nodeseterrors

Happy coding 👍

@dl-ias
Copy link
Author

dl-ias commented Mar 12, 2024

Problem is, that if you set general form error in first parameter(in correct way), and second as array, then it's also not shown. This is inconsistent. It should throw an error, or at least work correctly with general error.

@justin-schroeder
Copy link
Member

Sure, maybe we can throw a warning or something when you are in development mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug-report Bug is reported, but not verified by team ⛑ Needs triage The issue has not yet been examined by the FormKit team.
Projects
None yet
Development

No branches or pull requests

2 participants