Turf test environment

Hello folks, whenever someone creates an issue for Turf I always found annoying needing to run the posted code example locally to be able to see the result and try to figure out what’s going on; I have the impression that in most cases you just need to display the result on the map to understand the problem and I always reach for geojson.io to render the result of the code. Just so annoying.

Now, I came across this smart tool to help Carbon users and developers interaction when a new issue is created (their guided required procedure is excellent, foolproof!) and I thought it would be a very powerful tool for Turf as well.

So recently I have been working on an initial implementation of something similar for Turf: ~turf-sandbox.herokuapp.com~ https://turf-sandbox.netlify.app:

What do you guys think? Would you like the idea of making this a standard tool for helping people creating new issues? There are still few thing to do of course (the main one being how to select and load the Turf package(s) into the editor), but I wanted to have your feedback at this point before going further.

[mfedderly]

I’m not saying that we’ll never patch an old version, but right now the team is small enough that maintaining two major versions at once is likely going to be really hard. We’re doing a lot of work on the master branch just to bring it back up to date and make it easier to release.

[rowanwins]

Yeah not sure I’ve got any 😃 Roll with what you’ve got and perhaps it’s not a major issue anyway - there’s only one way to find out and that’s to use it