https://medium.com/@nextminds/replaying-bugs-with-flux-52f6bd8c8307 abour flux and replaying actions
either way, it's awesome!
You can't get that with angular with its two way bindings everywhere
@skidding what do you think about "fluxifying" your code? https://github.com/gaearon/redux-devtools - is out and this could really boost development on cosmos, and reduce on-boarding barrier as new devs could run your code and play with actions and states to uderstand it better, as well as you)
It would be great to integrate cosmos to redux-devtools actually, but I think it should be "fluxified" before. Git history integration (showing history of component on each commit, I talked about before) is also troubled without flux. But with it writing a plugin for cosmos is really easy.
As for the redux-devtools integration, I don't know what "fluxified" means
Don't focuse on this it is just my thought for future. I don't know straight way to do it now
Fluxifing means move all logic to event generation and updating cosmos on these events
@skidding Many of my clients argue against cosmos that it has not such automatization as unit tests despite that workflow is definetly better with it, so I made https://github.com/lapanoid/cosmos-mocha to solve this. It generates tests that checks that component at least renders on fixtures data(only props supported)
I have an error on react 0.13 boilerplate
I'm using react 0.14
how can I integrate?
Good news, just pushed a boilerplate for 0.14! https://twitter.com/skidding/status/667128832554569729
Ideally, I'd like an easy way to build an interactive playground site or let people clone a repo and have an interactive example they can easily run and play with.
The problem with the binary was that is was very much coupled with your local webpack config, so you'd end up merging bits of your local webpack config into the Cosmos internal webpack config, without having full control over the resulting webpack config used by the playground.
This became more difficult when Cosmos switched from react-hot-loader to babel-plugin-react-transform, because from what I could tell Babel looks for plugins under current working directory, wheres before I managed to hide dependencies inside the Cosmos package and include them via webpack's resolveLoader option: https://github.com/skidding/cosmos/blob/df29f2051a8619761101920605edfec62edad4f0/component-playground/config.js#L49-L51
The new boilerplate comes with a "npm run playground" cmd that you can run just as easily once you have everything set up, but I'm curious what do you have in mind. Contributions are definitely appreciated! @goatslacker
@/all wrote an essay on React Cosmos and its evolution, hope you like it: https://twitter.com/skidding/status/796718686631497730
Can anyone explain me the difference from react-storybook ?
Hi, I was wondering if I can change the fixtures folder name using a config parameter like fixturePaths (what I would achieve is to use a
fixtures sub-folder instead of the default __fixtures__) but I did not find a way to do this. I'm thinking about to open a PR where I will add a new config to make the __fixtures__ folder configurable, does it make sense for you?
hi all, i need my fixtures to be wrapped in a div with a certain classname on it. so i'm trying to use the html-webpack-plugin but when i run cosmos the fixtures diplayed have this string embedded rather than my the results of the template i'm providing the plugin:
/loader/2bbfc63244cae5233fe779fcdcbc9186.html
ah, got it!
i had to prevent .html documents from getting processed by file-loader
I am using the HtmlWebpackPlugin in addition to the AddAssetHtmlPlugin (because I am splitting dependencies) and executing a normal dev server works fine, as well as doing a normal compile with webpack.
However, using cosmos will serve the bundled /static/index.html and will thusly not inject my dependencies into the index.html -> Error on get /
However, using cosmos will serve the bundled /static/index.html and will thusly not inject my dependencies into the index.html -> Error on get /
@/all I apologize for neglecting this room. In light of the upcoming 2.0 release, we want to improve communication in the Cosmos community and decided to move the conversation to Slack: https://join-react-cosmos.now.sh/ – See you there!
Offending lines are ones like:
import Layout from './Layout'