Fork me on GitHub
#reagent
<
2017-03-10
>
oliy09:03:25

Hi all, does anyone know where the release notes for 0.6.1 are?

kauko09:03:42

https://github.com/reagent-project/reagent/commits/master from the commits it looks like it mostly updates react

juhoteperi14:03:36

@oliy Just updated changelog

juhoteperi15:03:36

@yogthos Can you also add me to the reagent-project org, so I can also update the reagent website?

yogthos15:03:45

@juhoteperi should be all set

juhoteperi15:03:28

@yogthos Thanks, now I just need to understand how the scripts in Makefile work 😄

yogthos15:03:06

haha yeah it’s a bit complex

yogthos15:03:18

I would vote just moving the site to cryogen in the future

juhoteperi15:03:20

Yeah. Not sure about cryogen but something new definitely.

yogthos15:03:40

it’s something to think about for sure 🙂

juhoteperi15:03:42

We've been thinking about trying mkdocs for Compojure-api, but Reagent has a bit different requirements as the docs should include live examples, and perhaps even Klipse.

yogthos16:03:14

I think integrating klipse would definitely be good

yogthos16:03:47

luckily that’s all clientside, so can just add the klipse js file in the template

yogthos16:03:14

that said, klipse is pretty hefty, so we probably wouldn’t want to have it load by default

yogthos16:03:25

maybe have a button or something on the page that switches it to live edit mode

gadfly36117:03:06

I agree about not having it load by default, don't want new users to confuse the load time with vanilla reagent/react

juhoteperi22:03:30

Phew, finally managed to build new version of the site

juhoteperi22:03:28

Had to do some changes to pre-rendering to separate code which requires reagent.dom.server from code used by browser, so React-dom-server is not included in browser JS file