Fixes attribute deserialization when using WebComponents | Fixes #292

[matuzalemsteles]

I've been looking at issue #292 and I've been noticing that the big problem of using boolean when it is false. In return of the function deserializeValue_ we have OR and as retVal gets false the return is value parameter that contains 'false'.

Note

There are some use cases that want to pass a number value to string, we can force it into the element attribute by passing "'10'", but the deserializeValue_ function receives ''10'' with two single quotes and breaks the JSON.parse, but the correct way would be to pass '"10"' to do the parser correctly.

Please feel free to offer a solution to avoid this.

Current behavior

Expected behavior

[matuzalemsteles]

cc @jbalsas

[diegonvs]

depends on #377

[yuchi]

@matuzalemsteles what’s that repl-ish thing you used to make those screens?

[matuzalemsteles]

hey @yuchi, I was using Scratches.