You can see the issue here, that instead of alerting with the property value tierrasdelcafe it is falling back alerting with Tierras del cafe which is the correct behavior when value doesn't exist.
https://svelte.technology/repl/?version=1.6.8&gist=c0a81f341a7652bbc68c129d0b0105d2
Checking the output I noticed that a line like this is missing option1.value = option1.__value in the renderMainFragment method.
I did some more investigation and found the problem at this line
Changing that line to this, resolves the issue.
if ( isBoundOptionValue ) {
local.init.addLine( `${local.name}.value = ${local.name}.__value` );
if (dynamic) {
local.update.addLine( `${local.name}.value = ${local.name}.__value` );
}
}
I have the code ready with a passing test for a pull request but wanted to consult before submitting it.
Thanks for this awesome project!
You can see the issue here, that instead of alerting with the property value
tierrasdelcafeit is falling back alerting withTierras del cafewhich is the correct behavior when value doesn't exist.https://svelte.technology/repl/?version=1.6.8&gist=c0a81f341a7652bbc68c129d0b0105d2
Checking the output I noticed that a line like this is missing
option1.value = option1.__valuein therenderMainFragmentmethod.I did some more investigation and found the problem at this line
Changing that line to this, resolves the issue.
I have the code ready with a passing test for a pull request but wanted to consult before submitting it.
Thanks for this awesome project!