NERDDISCO

I have a lot of different components that do different things on the data in the state by using reselect and I need the Redux store for using selectors. That's...

@tur-nr I was wondering: Why do we even need the `state-changed` event?

I had the same problem and @pixelass "fixed" it by using https://github.com/kolodny/immutability-helper instead of dealing with state changes on our own (even when we thought that we are creating immutable...

So what I tried instead was overwriting the `statePath` like this: ```js class TimelineScene extends ReduxMixin(PolymerElement) { static get properties() { return { scene: Object, sceneAnimations: { type: Array, statePath(state)...

This looks good to me right now and I the only "side effect" I can think of would be, that also every property that is created out of the `statePath`...

You should try https://github.com/tur-nr/polymer-redux/tree/polymer-3 because it was changed to not be in global scope anymore and to be a pure ES6 module.

So the only option right now to actually change an input type would be to reimplement it completely and then use it in a custom resolver, right?

That's an awesome idea and I will do it!

I will look into this! Thanks for reporting.

Sorry for replying so late, but I need some more time to figure out how to get the information from CodePen. If you want to take a look you can...