We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, passing in a field config with a nested input name throws an error when dynamicForms queries that input element in the DOM. For example:
let myForm = dynamicForms.makeForm({ fields: [ { name: 'options[showOnMobile]', /* ... */ }, { name: 'options[mobileSize]', /* ... */ }, ], rules: [ { name: 'options[showOnMobile]', update: [ 'options[mobileSize]' ] }, /* ... */ });
Will throw an error Uncaught DOMException: Element.querySelectorAll: '[name=fields[heading]]' is not a valid selector.
Uncaught DOMException: Element.querySelectorAll: '[name=fields[heading]]' is not a valid selector
It looks like this can easily be fixed by changing the way selectors are given to htmlElement.querySelector().
htmlElement.querySelector()
The text was updated successfully, but these errors were encountered:
2477a31
No branches or pull requests
Currently, passing in a field config with a nested input name throws an error when dynamicForms queries that input element in the DOM. For example:
Will throw an error
Uncaught DOMException: Element.querySelectorAll: '[name=fields[heading]]' is not a valid selector
.It looks like this can easily be fixed by changing the way selectors are given to
htmlElement.querySelector()
.The text was updated successfully, but these errors were encountered: