reasonml / reasonml.github.io Goto Github PK
View Code? Open in Web Editor NEWReason's documentation site
Home Page: https://reasonml.github.io
License: MIT License
Reason's documentation site
Home Page: https://reasonml.github.io
License: MIT License
I suppose this might require rewriting the guide as a tutorial
Auto-evaluating an accidental infinite loop caused by some intermediate editing state kind of sucks. Not just because the whole tab freezes, but you'll also lose everything you did up to that point. Even with the new localStorage, a kill & refresh will just land you straight back into the same infinite loop of suckiness.
So yea.. Timeout good.
just like http://bucklescript.github.io/bucklescript/js-demo/ does
For the playground we should just take https://github.com/BuckleScript/bucklescript-playground
If there is an error in execution of the generated JavaScript, the error will be displayed in the OCaml pane. Additionally, the JavaScript pane will be cleared, so you'll have no idea what even caused the error! ๐
On localhost this opens a new tab. On prod it turns into a left click.
cc @bassjacob
I suppose we don't have much of an answer yet, but the question keeps coming up regardless
This line produces an error
<span className="filter-label"><span>(ReasonReact.stringToElement "Has interface")</span></span>
Though if to format it manually like this, then it works:
<span className="filter-label">
<span>(ReasonReact.stringToElement "Has interface")</span>
</span>
So as you can see from error, it complains that code contains some reserved BuckleScript keyword.
P.S.
Was redirected from BuckleScript team: rescript-lang/rescript-compiler#1874
I realise the new proposed syntax #1299 is a bit of a minefield, but would it be possible to have an option on the Try page to explicitly select the WIP (with appropriate warnings, 'beta' status, summary of differences/changes, code-snippets showing real-life examples/advantages, etc) branch.
I would like to try it for myself before jumping to conclusions and the only way right now seems to download the repo, switch branch and use rtop/refmt or build and run the website locally. This may also help with testing, as people try to (a) understand and explore and (b) think up pathological case and (c) convince people of benefits.
Can consistently repro in Chrome and Opera
The first time I visit the site the title is empty (confirmed by viewing the page source)
Then when navigating around and going back home by clicking the site logo the home page title is the title of the previous page.
quickstart -> Quickstart
The overview is nice because it gives easy syntax tips. However, I cannot see (as a non-Reason-programmer) how my first program should look. How can I print values? Do I need a main
function? etc, etc
We can encode the snippet in the URL in the simple case
labelled argument with renaming + default value
Hi, as one of OS - windows user, I've been tried the different solution for installing reason on windows.
As last and most successful way which works mostly out of the box
is that package ocaml-on-windows.
Full IDE(vscode) support including merlin, refmt and other tools:
What do you think, should we add that package to documentation? I think it will help a lot of window-users newcomers.
I can make a PR
Right-click on a link on reasonml.github.io that points to somewhere else on reasonml.github.io.
I would be able to view the context menu for the link without navigation
My browser navigates to the link I right-click on.
This doesn't appear to happen on other sites using Gatsby (e.g., Segment's blog, https://www.gatsbyjs.org/).
I'm using Firefox 56 on Linux.
So that we could link to sub-sections in e.g. this section: https://reasonml.github.io/guide/language/types
It would be great to make use of the standard library in the playground.
let len = List.length [];
gets transpiled correctly into
var List = require("stdlib/list");
var len = List.length(/* [] */0);
exports.len = len;
Bucklescript Compilation Error
require is not defined
It will be nice to be able to upload a source file and extract it's code into the playground. My initial thoughts are we add a custom right-click menu by attaching it's event listener to the playground textarea(reason). Something like this jsfiddle.
If the error happens to be at the bottom of the pane, I guess you'll just have to live with it. (Alternatively you can add a few linefeeds at the bottom to push the code with the error up)
The share URLs are extremely long. It might be a good idea to base64 encode the query param value to make it merely very long. See reason-tools for inspiration.
Hi !
The new ReasonML's website is really cool, but I have point some little bugs :
\
in the codeI think it makes sense to add a next page button in the bottom right corner of each chapter/section. It gets tedious to scroll up (on small screens) after reading a section to find the next one.
We should debounce. Though the bucklescript playground is super fast... http://bucklescript.github.io/bucklescript/js-demo/
After clicking on some links really fast I eventually get SimpleEventPlugin.js:219 Uncaught TypeError: Cannot read property 'remove' of undefined
and routing no longer works.
I have a feeling that links to individual blog posts are going to break because they're just fragment identifiers on a single page.
Example tweet that is doomed to break when the index page gets too long or we change the link format: https://twitter.com/wincent/status/901116644600172544
Ideally we'd have standalone permalink pages with stable URLs which will last "forever".
maybe just hide the icon at mobile sizes?
OCaml's pprintast has some bugs (among other flaws). One of those bugs is that #
operators will be printed incorrectly. E.g.
let f thing => thing##x
will be printed as
let f thing = ## thing x
And because the playground compiles the pretty-printed OCaml instead of using the AST from refmt directly, it will fail to compile. When refmt is used normally as part of the build process however, it uses the AST instead and will compile correctly.
Before actually writing copy, I'd like to get feedback on a few suggested changes to the modules page in the language basics section.
Here's my proposal:
open
ing a module") to the purpose they serve ("Using code from another module").High pri. We'd like a deploy on master to be no-op (at least for the content itself) if the source isn't changed.
Not sure what we should do here. High pri, as many translations are coming in.
And maybe it let it float somewhere? It's nice to be able to stay on the page while searching
A few proposals for the quickstart section. I'm happy to do the work on these but wanted to get feedback first.
The last sentence of this section https://reasonml.github.io/guide/language/external is missing some words.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.