Bede Overend

+1

+1 I would love to see templatizer documented and maintained for public consumption. My particular use case is for constructing page layouts dynamically by passing templates to an element to...

Wel, that really sucks. Can you just transpile with Polymer CLI? Surely you can - and just partly bundle / code split? Anti-pattern to bundle _everything_, but also still advised...

Ah of course, forgot about the ES5 shim. Yeah I'd say we can start work on v1 conversions, that's not going to change, and have another look at best way...

> because the ES5 shim throws if you try and register an element with an ES6 class. So you can't mix ES5 and ES6 definitions. So I tried this in...

Have made a PR for the new element mixin in #86. @seaneking could you review?

It'd be great if we could land this earlier than 4, to unblock things like #84. We could just split out the current adapter, but keep it as a fallback...

Also should add tests to this branch before this is included in a release, just in the process of converting the old tests, but that can come after this is...

Oh other note - should we just have all mixins accessible at `simpla/mixins`? e.g. `import { Element } from 'simpla/mixins'` EDIT: Actually probably not, because we're compiling as a UMD...

@seaneking would you be able to setup the build for that? Been awhile since I've setup a gulpfile, particularly not with the new version. We'll need that to pipe it...