Fork me on GitHub
#re-frame
<
2016-10-03
>
andre10:10:10

0.2.0 with the debugger in the separate browser window released

andre10:10:47

time travelling in the next version

shaun-mahood16:10:00

@andre: I get the following warning when running re-frisk

WARNING: Namespace re-frisk.debugger contains a reserved JavaScript keyword, the corresponding Google Closure namespace will be munged to re_frisk.debugger$ at line 1 resources\public\js\compiled\out\re_frisk\debugger.cljs
- is that expected?

andre16:10:28

@shaun-mahood yes. i saw it only after i published release. i'll fix it in the next release. thank you

dobladez18:10:44

Any docs/pointers to migrate from 0.7 to 0.8 of re-frame? It's a small prototype I want to migrate

shaun-mahood18:10:42

@dobladez: Did you define any custom middleware? If not, just change the version and it should work.

shaun-mahood18:10:09

Or are you looking for specifics on changing from the old syntax to new?

dobladez18:10:40

@shaun-mahood Thanks, cool. No custom middleware. I want take advantage of the new stuff

dobladez18:10:49

I just found the new "in-progress" docs... going through them. I was wondering if there were quick pointers comparing the old vs new

dobladez18:10:19

I do see some notes here on slack, but couldn't yet find info on the wiki

shaun-mahood18:10:38

And there is a lot built into the new docs

dobladez18:10:50

ah, duh... in the changelog, right? who would have thought of that?! 🙂

dobladez18:10:14

sorry, thanks again

shaun-mahood18:10:42

You aren't the only one - I've been trained to expect almost no detail in changelogs

shaun-mahood18:10:24

@andre: I'm having some trouble getting re-frisk to work in a separate window, pretty sure I'm doing something stupid. New version works fine in my app panel if I configure it that way. I've added refer-macros, run export-debugger!, and have added the :external config to my project.clj under cljs -> builds -> dev -> compiler Is there anything else that needs to be done? I've gone through the re-frisk repo but can't see anything different.

andre18:10:43

is the debugger button appear?

andre18:10:53

button with the arrow

andre18:10:29

if you are using figweel sometimes you need to call (reload-config)

andre18:10:39

after changing project.clj

shaun-mahood19:10:06

@andre: Thanks, that helped me figure it out - I took away the enable-re-frisk! call in my run command when I started trying to get the external window, so the debugger didn’t come up at all. For whatever reason I thought you had to do one or the other, it’s great to have both of them.

micmarsh19:10:53

Are there any established standards or processes for contributing our own effects libraries? I've been working on https://github.com/micmarsh/re-frame-youtube-fx and want to make sure it's consistent with the re-frame "brand"

shaun-mahood19:10:31

@micmarsh: Check out the very end of https://github.com/Day8/re-frame/blob/master/docs/Effects.md - that’s all the guidance I know of at the moment.

shaun-mahood19:10:38

Awesome that you’re working on that, too!

micmarsh19:10:26

ah, cool, thanks Shaun!

micmarsh19:10:28

very cool @madvas! I used to be very into Blockchain stuff, this should be a fun read

johanatan20:10:41

Hi, sorry if this is covered somewhere and I vaguely remember something like it being covered but... is it possible to have a parameterized reaction?

shaun-mahood20:10:46

@madvas: Awesome. If you want to add your effects libraries to the end of https://github.com/Day8/re-frame/blob/master/docs/Effects.md while you’re at it, feel free!

madvas20:10:39

yep, I wanted to do that also 😉

madvas20:10:29

Just wanna to point out that re-frame 0.8 is pure awesomeness. Had a lot of fun using it, while creating Ethereum apps. Big Thanks to all contributors 😉

shaun-mahood21:10:27

@madvas: Thanks for the PRs, I screwed up merging yours and another one and ended up applying the change manually. So the declined PR is really an accepted PR, just blame it on my lack of Git skills / confidence 🙂

shaun-mahood22:10:46

@andre: Not sure if this is a good idea or not, but I think it would solve one of my general re-frame development issues (and I'll probably pursue it with frisk if it's not a good fit with re-frisk). When I'm working on new functionality, I tend to use a lot of println statements to double check and verify my assumptions about how the data is flowing (probably not ideal, but it's the one debugging tool that's stayed relevant across every platform and language). I'm wondering if it would be possible to add in a sort of one-time display, so that I could add (re-frisk/one-time-log x) and have an extra entry added to a logging section of re-frisk (or just at the bottom). Then ideally I could look at the data, then close/remove that log entry and move on to the next one.