On Sunday, March 15, 2015 at 6:09:16 AM UTC-5, Scott Nelson wrote: > I’ve been using React Router (https://github.com/rackt/react-router) with > JavaScript and like the way that you can map nested routes to nested > components (similar to the Ember.js router or AngularUI router). I’ve missed > this with Om + Secretary and came up with the following: > > https://gist.github.com/scttnlsn/7018b128032b73ce187e > > I’d love some feedback here. Is this a decent approach?
yea, i was thinking about putting route information in app-state as a string or array or something. the gist is very helpful! i see that some projects, like https://github.com/circleci/frontend use an async channel stored in app-state for routing, which might (?) make routing run faster or have some other advantages (???) for larger apps. it is slightly worrying that they don't use secretary's named routes as in your example, but perhaps that wasn't a feature secretary had implemented when their project started. indeed, i got the feel that it's a codebase that's undergone a lot of changes even before noticing that there are 13,000+ commits. i like the idea of keeping route information as a data structure nested directly into app-state, tho, for smaller applications, at least, and also wonder what more experienced developers think about it. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
