search

ffxsam / ffx-meteor-react-boilerplate

Meteor 1.4 + React boilerplate (DEPRECATED/ABANDONED) 👋
133 stars 20 forks source link

Example app #10

Open Morganjackson opened 8 years ago

Morganjackson commented 8 years ago

@ffxsam Thanks for all your work on this awesome boilerplate! This finally made things click for me.

Do you plan to update the example app to use createContainer() or one of the many other options? I'm very interested to see how this works with your boilerplate.

ffxsam commented 8 years ago

I'm really glad to hear you found it useful! And yes, the example app is in sore need of an update. :) I'll leave this issue open and post again once it's been updated.

peterpetre commented 8 years ago

What do you plan to update on the example branch?

majochoc commented 8 years ago

I like the structure of the example branch. Its similar to meteor-react apps I've already built. Will the example branch be moving to a structure similar to master with an imports folder and explict imports from the startup folder? Have you discussed this somewhere in another thread I missed? I don't understand the benefit of the imports structure in master.

ffxsam commented 8 years ago

Sorry, been completely swamped with projects. I'll get around to updating the example branch at some point!

Will the example branch be moving to a structure similar to master with an imports folder and explict imports from the startup folder?

Yes.

Have you discussed this somewhere in another thread I missed? I don't understand the benefit of the imports structure in master.

Not discussed anywhere yet. I ran into some trouble on a project where I wasn't using imports—things basically being loaded (or not!) at the right time. So I realized I needed to just short-circuit any lazy-loading done by Meteor, and I put everything in imports. It still needs some restructuring, actually. There should be client and server folders, because unit testing breaks in some cases.

majochoc commented 8 years ago

Thanks for the response. I was wondering if you ran into trouble, because I had read in another issue thread how you had hoped to avoid the imports folder since its almost certain to go away post 1.3.

ffxsam commented 8 years ago

I'm hoping at some point, Meteor does a way with lazy loading altogether. That might be the eventual goal, but I don't know for sure. For now, it's strongly recommended to use the imports folder.