We're looking forward to hacking with you on Reason in a few days! This document should get this set up and provide some guide on what we'll cover this Friday.
- Join the #events-and-meetups channel in Discord and ping @sgrove when you're there so he can check you off the list
- Set up Visual Studio Code (vscode) with the excellent ReasonML extension.
- Git clone the hello-reactive reason project (this repo) and confirm that vscode is working properly and you can recreate the screenshot below
- Fill out the pre-workshop survey
- Post any questions you might have, or upvote questions you're interested in on our sli.do (the event code is #J454, in case you need it)
By the end of the workshop, we want you to be able to:
- Read/write basic React components Reason
- Call out to JavaScript from Reason
- Add Reason code to existing client-side JavaScript apps (call Reason from JavaScript)
- Reach out to through community channels to get effective help in a reasonable amount of time
In short, we want you to know enough to start building real things for existing projects, and to know how to get around any roadblocks that come up.
This is a four-hour workshop with forty people each, a handful of volunteers helping out, and a lot of material to cover. We know this is a busy time, but we need everyone to stay on top of their game and help us out. To that end, we have 5 must do pieces of homework before the workshop - and the sooner the better.
Everyone should install Visual Studio Code (vscode) so we have a uniform experience. Once that's set up, please install the fantastic ReasonML package. Ask in the discord (#editorsupport) and let us know that you're prepping for the workshop if you have any problems at all.
We want to make sure that your editor and the Reason extension are both working well now:
git clone git@github.com:sgrove/reactiveconf-2017-reasonml-workshop.git
cd reactiveconf-2017-reasonml-workshop/hello-reactive
npm install
npm start
npm run webpack # In another tab, since npm start is still running
code src/simple/page.re # In *another* tab, open vscode from the hello-reactive dir
Now when you hover over make
on line 17, everything should look like the editor screenshot below: