I didn't find any bug report on that, so sorry if that already been answered ;)
I read that gopherjs is mostly trying to follow es5 for compatibility (#320). It makes sense. However, wanting to create new bindings for the upcoming Polymer 3 with lit-html support (https://github.com/Polymer/lit-html), there are two main things with those technologies to create webcomponents in go:
…
) are parsed by javascript, returning them raw or wrapped would be needed as they can have interpolation and nesting.So, I'm seeking up for advices for how achieving that, and which road sounds the sanest to you (gopherjs, generator + trying to generate source maps, or … ?). Thanks!
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4