#pyramid

at least redux provide sit through reselect

You know, I haven't seen a new JS framework announced for several weeks. Must be the holidays.

hehe

blaflamme: you know a lot of that stuff is done by martin faassen right?

reselect is faassen

right I saw that

I just found it entertaining how we're all drawn to the same stuff

I haven't needed reselect yet, but I have a feeling that it will come in very handy shortly =)

yeah I haven't used it yet either

to me it seems like a perf optimization I haven't needed

in nuclearjs it's the way to access your store stuff

the store is not passed down, so you observe through getters

You shouldn't pass the store down to your component in Redux...

Only your top-level should be redux aware, and that gets passed down the store, it selects entities out of it (immutable) using functions or anything you want really, and then those are passed as props to your main component.

you store is built from your reducers and the store is pass from <Provider store={store}>

That's just a wrapper.

<Provider store={store}><RootComponent /></Provider>

then you use connect() on your RootComponent

which selects what state it requires out of the current state from the store.

Your root component at that point has this.props.

http://rackt.org/redux/docs/basics/UsageWithRea... scroll down to Connecting to Redux

it explains what is going on.

finally react 0.14 fixed stupid HOC ownership issues

what a pita

?

don't worry about it ;-)

You know that sentence you just posted is not very google-able either...

sorry got a phone

yeah right, I know

but the wrapper passes the store to make your selector works when you connect them

basically in react < 0.14 the context was very screwy so your code example you just pasted wasn't so pretty

context is still undocumented amusingly

context is still not recommended, api could change

despite router/redux/etc being heavily dependent on it

yeah but router advoate to still use mixins

funny

ES6 based classes don't allow for mixins.

So they are mostly going away.

NuclearJS in it's documentation still uses React.CreateClass

with a mixin.

yeah, like react-router

any idea why with python setup.py develop I have something like -e git+git@xxxx:<git username>/xxxxx.git when I pip freeze -l ?

I haven't used any mixins in my use of react-router.

probably till context is the thing

can do the same with nuclearjs, usng a tiny wrapper

mage_: pip freeze looks in the linked folder and finds a git repo there

I'm deploying in production with salt and one of the step I do is python setup.py develop, but then the (private) repository (with login, password ...) is visible when I pip freeze -l

x58 https://github.com/rackt/react-router#whats-it-...

x58 uses createClass

any idea how could I avoid that ?

blaflamme: Ah, yes, but those can easily be replaced with ES6 classes,there are no mixins.

mage_: I think you just have to grep it out or not use setup.py develop

mixins are no longer supported.

do you put the .egg-info in the git repository .. ?

in reactrouter? yes they are

blaflamme: I am talking about React using ES6 classes does not support mixins.

mage_: no

oh... of course, ES6 classes don't support them

but react still support createClass, no deprecation warning still

raydeo: so when you deploy in production you do a setup.py develop/install every time you redeploy the webapp ?

a develop, yes

React-router does not require the use of mixins. NuclearJS it looks like the only way to get access to the store through it's getters is to use a mixin... or write a custom wrapper.

ok :) thanks

x58 a wrapper from the same team is available

mage_: I do python setup.py bdist_wheel and copy the wheel to prod, and pip install the wheel.

Ah, okay.

so you end up with something similar to redux for the initial setup

x58: maybe it's better than doying setup.py develop

That's up to you :-) I do it that way because I think it's simpler, and I keep the files around for archival purposes.

I'm busy to automate everything with salt (and I'm not a packaging expert ..)

I use SaltStack for deploys.

same here

stupid question, is it really necessary to have .pyc files for a pyramid webapp ?

as necessary as in any other scenario I guess

the only advantage I see is when the webapp is started the first time

mage_: .pyc's are just compiled .py's