Fork me on GitHub
#om
<
2016-02-14
>
futuro00:02:45

@hueyp: good point, thanks simple_smile

jamesmintram17:02:01

Are there any articles/pointers about how to do browser routing for SPAs when using Om Next?

iwankaramazow17:02:24

@jamesmintram: you're pretty much on you own right now You can take a look at https://github.com/jdubie/om-next-router-example https://github.com/omcljs/om/wiki/Routing-Support

iwankaramazow17:02:45

I'm working on a router right know, with a bit of luck I'll open source it within the next two weeks

jamesmintram17:02:35

@iwankaramazow: Hey, thanks! That is useful to know! So currently I am using a map which contains the current view ID and any associated params. This is obviously pretty limited but seems to work. I’ll take a look at those examples, and look forward to seeing your work!

futuro18:02:55

Hey all, has anyone encountered issues setting functions in the componentDidMount part of the lifecycle?

futuro18:02:04

specifically, I'm having difficulty with the following line https://gist.github.com/futuro/22536021c58d1716a021#file-timepicker-cljs-L25

futuro18:02:00

I'm creating two different TimePicker components in the CreateEvent component, but both components pass the same function to js/TimePicker.

futuro18:02:37

so instead of calling set-beginning or set-ending depending on what value is passed in as :dbkey in the props, the order in which I call the factory functions sets the function both components calls

futuro18:02:16

and I'm at a loss as to why this would be happening

futuro21:02:37

I'm even getting this behavior when I create two completely separate components, factories, and mutation functions