Multiple Attribute Throws error
See original GitHub issueHi thanks for this great project. I’m using version 2.0.10 and ran into an edge case that’s throwing an error. The problem is here and caused by modelValue
being null.
modelValue
is null because I wanted to reset the select to nothing as a cancel button has been clicked. Maybe checking for it’s existence on the offending line or defaulting it to an empty array might fix the problem.
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Exception when getting attribute constructor arguments with ...
The problem seems to be the parameters passed to the Test attribute constructor. If one of them is null, ConstructorArguments throw an exception...
Read more >Attributes and Error Handling
Attributes allow specifying and handling timeouts and handling errors and cancelations. An attribute has a name and a value. The syntax is: name:...
Read more >Vpc multiple attributes modification is giving exceptions #415
Vpc multiple attributes modification is giving exceptions #415 ... Exception: InvalidParameterCombination: Fields for multiple attribute ...
Read more >HTML attribute: multiple - HTML: HyperText Markup Language
The Boolean multiple attribute, if set, means the form control accepts one or more values. Valid for the email and file input types...
Read more >Follow-up -> ERROR: caught BioMart::Exception:
... Query ERROR: caught BioMart::Exception::Usage: Attributes from > multiple attribute pages are not allowed >> genes_map4 <- getBM(attributes=c > ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ll review this
Thanks for the reply @lordfriend in my case the quick fix was mostly to remove the possibility of getting an error thrown in the console and yes I have to say that I only changed the line that throw an error on my side. We want to avoid having code throwing error. If we look at the
viewValue
variable, then the only other place that it could throw an error is on line 1326.So in the end, that would be 2 lines to change to avoid error thrown
and next line
This does not change the behavior of the code in any sense, except that it won’t throw false error when
viewValue
isnull
and the UI won’t be broken anymore, apart from the select being empty.Thanks for your plugin, I now use it in all my projects 😃