Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Planning 24/01/17 #5

Closed
my-slab opened this issue Jan 10, 2017 · 5 comments
Closed

Planning 24/01/17 #5

my-slab opened this issue Jan 10, 2017 · 5 comments

Comments

@my-slab
Copy link
Contributor

my-slab commented Jan 10, 2017

Week 3 24/01/17

If you have anything you want to present, discuss as a group, or see presented, please comment here.

Things we didn't get to last time:

  • MobX

Agenda

@my-slab my-slab changed the title Planning Week 3 24/01/17 Planning 24/01/17 Jan 10, 2017
@alexhayes
Copy link

I (or David) could potentially do a talk about my Self Contained App (SCA) idea that we've used on BPCLE and AFD. It's probably not so relevant to JS more relevant to general maintainability, portability, code structure etc...

I first proposed it in react-redux-starter-kit PR 682 because I wasn't a fan of the way react-redux-starter-kit split natural grouping of "app" files across the file system.

The idea is very similar to the way Django (and many other projects) does things, you have an app which contains all the things for that app. You don't have a single views directory which contains all the views, a models directory for the models etc...

Ultimately react-redux-starter-kit didn't go with my approach but they went for something very similar called Fractal Project Structure which opts for a deeply nested app structure rather than a single level deep like I proposed in SCA.

@my-slab
Copy link
Contributor Author

my-slab commented Jan 11, 2017

Yeah that would be sweet @alexhayes

@timmygee
Copy link

I'd love to talk webpack configuration more. It's still a bit of a mysterious beast to me.

I've been trying to get my own project running with react-toolbox, hotloading, css-modules and all the latest babel ES-things. Simply adding those items in hindsight of an existing webpack config is perilous. Perhaps a discussion around common pitfalls and solutions could be worthwhile. I'll know more by the next talks so perhaps I can present how I went about the problem myself and compare that to understood best practices etc or whether we should just use @fruuf's https://github.com/fruuf/pack for all the things!

@shangxiao
Copy link

Looks like @fruuf is using webpack 2, is that much of a change?

@my-slab
Copy link
Contributor Author

my-slab commented Jan 13, 2017

@fruuf is okay to do a talk on pack. Seeing it is used in two or three projects it's probably worth demystifying that a little bit. Maybe you (@timmygee) could list the things that you found to be pitfalls when working with webpack and could go through them.

@my-slab my-slab closed this as completed Jan 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants