You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a improvement suggestion, let define this scenario:
in controller : model.intList = [1,2,3,4]; model.anotherIntList = [1,2]
in html: <... data-ylcLoop="int: intList" data-ylcBind="prop.checked: otherIntList.indexOf(int) != -1"
After an event that needs to remodel the html, intList changes to ["1", "2", "3", "4"], hence breaking the condition in the html and it always evaluates to false.
There are some ways to circumvent this problem, but it would be great if the library could just keep the original element's types.
If too difficult, why not supporting parseInt in the html attribute?
Thank you very much!
The text was updated successfully, but these errors were encountered:
Hello,
That's a good point, thank you.
I have committed a fix for this problem - the original model type should now be preserved when doing the view-to-model synchronization. Release 0.99.12 includes the fix, please go the official website to download it.
Hello (and thank you for your awesome work)!
I have a improvement suggestion, let define this scenario:
in controller :
model.intList = [1,2,3,4]; model.anotherIntList = [1,2]
in html:
<... data-ylcLoop="int: intList" data-ylcBind="prop.checked: otherIntList.indexOf(int) != -1"
After an event that needs to remodel the html, intList changes to
["1", "2", "3", "4"]
, hence breaking the condition in the html and it always evaluates tofalse
.There are some ways to circumvent this problem, but it would be great if the library could just keep the original element's types.
If too difficult, why not supporting
parseInt
in the html attribute?Thank you very much!
The text was updated successfully, but these errors were encountered: