Echo JS 0.11.0

WTF!?!?  Article submission, to summary page on medium that links to the article...

That said, this is part of what I don't like wrt angularisms..

    expiry: ['', [Validators.required, Validators.pattern(expiryRegex)]]

Why does it even need nested arrays, the first item is the current value, just have the rest be validation..  Or better uet, have it be an object, that you pass an array of validators to.

    expiry: validatedValue({
      value: '',
      validation: [
        Validators.required, 
        Validators.pattern(expiryRegex)
      ]
    })

I know I could make that function... I just mean that ng2 chose TypeScript so that they could have enforced structure and types, then they use this weird array structured dsl in places.

Really wish it didn't cost karma to vote down... it's hard to earn it on this site.

There doesn't seem to be a check for the chunks being valid via hash, so that's a security concern.  That said, it's a pretty nice idea... though piggy backing on web-torrent via published hashes would work too.

https://github.com/PixelsCommander/ViralJS/issues/5

flatmap is just map + reduce

    invoices
      .map(inv => inv.positions)
      .reduce((a, p) => a.concat(p || []), []);

ex:

    function flatmap(object, mapper) {
      return object.map(mapper)
        .reduce((agg, ary) => agg.concat(ary || []), [])
    }

For me, read everything you can, try to remember the bullet points, and later on, when you have a chance or use case, give it a try.

Some things take more buy in... React can be brought into a project in pieces... but after a while, you're best off with other tooling in addition, Babel and a bundler become nearly indispensable (it took me a while to warm to Webpack over Browserify though).

It's not *really* stateless, it's just the state is served via properties on the component.

I was just arguing with a coworker a few days ago that "async" functions were imminent, and since we're using babel anyway that we should go ahead and use them.

This sounds similar to how the `react-icons` package works, in fact, many of those components could have been used to wrap their own SVG icons.

I don't have anything... I had to do some checks for the actual route, the router, and in the redux engine... It was about 6 months ago tbh and I just remember it was wild getting it to sync between the router and the redux... I had to hack a listener for route changes, then trigger an action into the store.

I'm not longer working in the group that was on the project...

One of the hardest issues I had with redux + ng2 was actually trying to integrate the ng2 router with redux, I wanted to keep the route and params in redux, so that my components could all reference from the same location for all state.

Keeping the store and router synchronized was pretty painful to say the least...  Hopefully the next article in this series touches on that.