Fork me on GitHub
#re-frame
<
2017-10-18
>
yury.solovyov08:10:06

How should I generate links for my routes with secretary? it works if I use (secretary/dispatch! "/landing"), if I actually render same link and click on it, nothing happens. Should I listen for history events manually?

yury.solovyov10:10:29

@lovuikeng I switched to funcool/bide

yury.solovyov10:10:55

it is a bit more automated

lovuikeng10:10:24

nice @yury.solovyov pure data, another great lib from funcool 👍

kah0ona13:10:37

Hello friends, I just released my first re-frame lib, would love to take comments. I needed this functionality for a project, but thought I’d make it into a library. https://github.com/Kah0ona/re-dnd

jhund14:10:50

@kah0ona very cool! I am in need of a solution for d&d in my re-frame app and will consider your library. I just skimmed through the code and noticed that you’re using a hard-coded location in app db to store state related to dnd (`:dnd/state`). That triggered the following thoughts: Should the location in app db be configurable (with a sensible default) to avoid conflicts with existing namespaces? Or what if there was a re-frame convention where all libraries have a dedicated location in app db and then use github-project or reverse-domain notation? In your example, the path into app db could then be, e.g., [:libs :kah0ona/re-dnd :state].

kah0ona14:10:31

yeah i was thinking about that…

kah0ona14:10:00

good idea.

danielcompton15:10:08

Reverse domain notation would match best practices for namespaces

deg16:10:55

Reverse-domain is a fine idea, but I do something easier in re-frame-firebase: a namespaced keyword of my internal namespace, so I use :com.degel.re-frame-firebase.core/cache. This has the advantage of being trivial to code.

deg16:10:43

@danielcompton - but I think you are saying the same thing; we just disagree on what "reverse" means.