-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preparations for the BuckleScript v7 transition #3914
Comments
PPX Upgrade tasks |
Thanks @swuecho. Added above. |
@ryb73 has updated their ppx to support (only) BuckleScript 6.x: rescript-labs/decco@2d68883 Also |
@gaku-sei I have update the description on top. |
Thanks @alexfedoseev , added. |
@Coobaha thank -- added above. |
@cristianoc plugin is ready since v0.76 (although I found there is a small update to release to adapt it to bs-6.2.1) |
@giraud great thanks. Once a version compatible with bs 6.2.1 is released, I'll update the description on top. |
bs-deriving works with BuckleScript v6 (tested with version "44.1.0") Side note: Same version of reason-macros works with both v5 and v6. I'm curious how this works? Until now I was never able to use the same ppx binary on different AST versions |
@osener thanks for the uppdate. For |
Ah thanks. I had forward-compatibility in mind when I wrote that, but of course OCaml 4.06 AST is nothing new. |
|
|
|
lenses-ppx might be worth mentioning in the upgrade guide, as it is used in the beautiful ReForm library. According to their Readme, I think they support v7. |
This issue is used to keep track of important tasks to make BuckleScript v7 (OCaml 4.06 based version) the default package on npm.
Transition Philosophy
As soon as BS@6 is live, every user should be able to just use our migration guides to upgrade their existing BS@5 based projects to the newest versions. For the most important tools, there should be an equivalent release for handling 4.06 based compile artifacts.
Those tools are mostly PPXes which are based on the 4.02 Parsetree. Our recommendation for PPX maintainers:
As a proper example, check out genType.
GenType introduced a detachedIt uses the4_02
branch so it can still provide crucial bug fixes for 4.02 based versions, but it will not provide any new features to make sure users upgrade soon and we can deprecate 4.02 once in for all.v2.*
versions for BS@5 releases, andv3.*
for BS@6.Update: Gentype already dropped the workflow for a 4_02 hotfix-branch completely, since it is too much effort rebasing the diffs
PPX Upgrade tasks
This is a non-exhaustive list of tools which need to be handled, otherwise a lot of people will be stuck (please let me know if you know of any other tools):
[] graphql_ppxCurrently forked in https://github.com/baransu/graphql_ppx_re
Could be moved to a different domain and renamed.
Example conversion PR: Build with Bucklescript 6.2.1 based on OCaml 4.6.1. pupilfirst/pupilfirst#103.
Updated the ppx to support (only) BuckleScript 6.x: https://github.com/reasonml-labs/decco
bs-log
A ticked box means that:
Editor Plugin Tasks
BuckleScript v7 Migration Guide
For the official transition, we should prepare a migration guide which communicates:
refmt
versionSince v7 comes with the new
records-as-objects
feature, we will need to update theObject
related docs section as well. (See PR).Revamp the BuckleScript Object documentation
Pending PR: https://github.com/BuckleScript/bucklescript.github.io/pull/184
Object
/Object 2
docs to something more meaningful and communicateMaking it public
We should make sure to communicate the switch on every channel:
\cc @anmonteiro @baransu
The text was updated successfully, but these errors were encountered: