Fork me on GitHub
#re-frame
<
2018-03-15
>
timo11:03:20

@mikethompson now I am still using the (fn [] in line 81 but removed the @ as you proposed in option 2. The update is still not happening automatically...so I have to use :component-did-update to cope with my updates, right? @mccraigmccraig

p-himik11:03:55

@timok You replaced all usages of open-tours and other subscription values with @open-tours, right?

p-himik11:03:20

So it became e.g. (:tours @errors) instead of just (:tours errors).

timo13:03:56

@p-himik yes (EDIT because confused)

p-himik13:03:29

@timok Can you share the new code for map-page, just in case?

p-himik13:03:14

@timok What does that defn do inside map-page? I think you want to write just [:ul ...]. In any case, that shouldn't be the cause, so I don't have other suggestions at the moment, sorry.

timo13:03:17

@p-himik 😳 right, that shouldn't be there

timo13:03:54

I will go with component-did-update (like mikethompson said) because it seems plausible that one has to implement it when using non-react-components...still new to this stuff...

p-himik16:03:09

@timok Maybe you could create and share a small repo with a reproducible code?

timo17:03:11

@p-himik will try to... is quite some effort because the map-api I am using is closed so I need to implement a different one but let me see...

timo17:03:17

thanks so far

timo18:03:02

@p-himik I wrote it with an osm-implementation and pushed it here: https://github.com/TimoKramer/leaflet-reagent-reframe

timo18:03:01

It is updating the state in the leaflet-map but doesn't rerender the component somehow

timo18:03:20

I will be back tomorrow

timo18:03:22

I guess it is something leaflet-specific

timo18:03:47

State in the leaflet-object or so