These are chat archives for ractivejs/ractive

24th
Aug 2017
Bob Schellink
@sabob
Aug 24 2017 18:09
What is the general workflow to develop a new feature for Ractive? Say someone logged an issue with a jsfiddle that shows a problem with the parser. Do you copy the fiddle to the sandbox folder and run "npm run dev:browser" and debug in the browser?
Joseph
@fskreuz
Aug 24 2017 18:11
You just run npm start (just an alias to npm run dev:browser) then stick the code in sandbox/index.html (create additional files as needed) then view http://localhost:4567 :grin:
Chris Reeves
@evs-chris
Aug 24 2017 18:11
If it's a bug, I usually poke at the fiddle through dev tools until I figure out what's wrong. Then I distill a test case locally.
Joseph
@fskreuz
Aug 24 2017 18:14
Sometimes debugging in jsFiddle is a pain tho. Too much going on.
Chris Reeves
@evs-chris
Aug 24 2017 18:15
yeah
the playground is a bit better
fiddles in non-js can get quite confusing too
Bob Schellink
@sabob
Aug 24 2017 18:30
sounds easy enough ;-)