mysterious REPL behaviour when using lens named "name" about ramda.github.io

[CrossEye]

Yes, it's bizarre, but there are several odd quirks in this REPL. It really could use some love. Anyone interested in taking it on?

@raine? @davidchase?

[davidchase]

not an issue with ramtuary http://goo.gl/TyHqZ7 😝

so i guess the question if you guys would like to include ramtuary in place of ramda repl, what is expected?

i can PR it minus the sanctuary and ramda-fantasy stuff, you probably don't need the babel polyfill or maybe you would like it?

i also bundle it with browserify but there's always the potential of using rollup instead

thoughts?

[CrossEye]

Actually, I'd prefer to keep most of the Ramtuary functionality intact. I think including Sanctuary and Ramda-Fantasy would be an improvement (although it would be really nice if there were checkboxes to turn them off.) And Babel would be a step in the right direction. I don't care much between browserify and rollup. I've not yet even tried rollup, to be honest. The one important thing I don't think is there now is a version selector for Ramda.

I'm not looking for all this -- certainly not now -- but in my ideal world this would be skinned to look like any other page on http://ramdajs.com, living perhaps at first at a different path (/try ?) until it seemed ready to be the main REPL. Even better would be if, when we decided to point the path to this version, old links would continue to work in the new version; if there was a Ramda version in the URL, it would be included, and Sanctuary and Ramda-Fantasy would simply default to latest. That might be too much to ask for, though, and I wouldn't let not being able to do it stop me from improving the REPL as we can.

My bigger dreams includes something that might not be possible, but could be very useful, if the REPL would output more than the last expression. Perhaps it could respond to the same token we use in our examples: //=>. This would also be very useful in letting us automatically link code examples from the documentation to the REPL.

So I discussed all sorts of possible extensions. Honestly, if we could simply port over the existing code onto the Ramda site, I'd be thrilled.

[davidchase]

thats sounds great i like those ideas... i will try to send in a PR tomorrow during day but most likely after work 👍

[CrossEye]

Wonderful! Please let me know what I can do to help.

[buzzdecafe]

🎉

i much prefer the ramtuary repl and would love to see it replace the current one sooner rather than later. In fact, right away. Then the rest of the items on @CrossEye 's wish list can be integrated ad libitum.

[CrossEye]

@buzzdecafe:

Agreed; the only thing that gives me pause is all the links to the current REPL that will be completely useless if we don't support the version in the URL.

[davidchase]

sorry didnt have chance last night, got swamped... forking the repo now... 😄

[davidchase]

quick update, i was able to port over the repl to the ramda fork, but babel is giving me some issues so i will try to resolve that before submitting a PR

[davidchase]

PR #44

[buzzdecafe]

this issue looks fixed to me