🚀 Miriad is hiring — UX Designer / Front-End Product Engineer (ReScript)
Sure, email me on paul@miriad.studio!
View ArticleClik here to view.
Even more JSX customization
A few times I wanted to override the original domProps type, but it’s cumbersome to do it, since its huge and you can’t override existing fields in a type. So I made a PR to split the type into...
View ArticleReScript v12 js-post-build confusion
absolute paths would be fine, in fact preferred! Thank you!!
View ArticleReScript v12 js-post-build confusion
Great, you can try this out in v12.1 Let us know how it goes!
View ArticleWhy are text nodes in jsx interpreted as symbols?
I’m still interested in turning this around, please chime in on Revisit JSX syntax · Issue #8053 · rescript-lang/rescript · GitHub and vote on the issue. Add comments pro and contra to the github...
View ArticleClik here to view.
Why are text nodes in jsx interpreted as symbols?
they’re wrong React.string makes more sense, is more explicit, more greppable and if you’re dealing with internationalization, not even noise (just put it in your i18n pipeline).
View Article[ANN] Sunset of legacy build system
Dear community, For the next major release our plan is to sunset the rescript-legacy build system (internally named bsb) and completely replace it with the new build system announced in rescript 12....
View Article[ANN] Sunset of legacy build system
I’m finding that issue difficult to understand, what exactly is the list of features that would currently disappear?
View Article[ANN] Sunset of legacy build system
The section under Questions for Team Discussion Rewatch explicitly lists these as unsupported in UNSUPPORTED_TOP_LEVEL_FIELDS: ignored-dirs generators cut-generators pp-flags entries use-stdlib...
View ArticleWhy are text nodes in jsx interpreted as symbols?
For me, part of the appeal of ReScript is safety. So I have no complaints about this at all. Having a completely sound type system is what differentiates ReScript from TypeScript.
View Article[ANN] Sunset of legacy build system
I think you can already remove use-stdlib and external-stdlib from that list, both are leftovers. use-stdlib is not implemented anymore even in bsb, and external-stdlib does not make any sense anymore...
View Article[ANN] Sunset of legacy build system
Ok thanks! The only one we use is reanalyze but we don’t really use that, I’m totally confused on the state of reanalyze anyway. We have yet to try out the new js-post-build which has been the only...
View Article[ANN] Sunset of legacy build system
There has been a rewrite of reanalyze to be fully reactive and it should now be possible to use it in monorepos as well. We’ll release a blogpost about it as soon as the tooling/editor integration is...
View ArticleWhy are text nodes in jsx interpreted as symbols?
I’m in two minds on this. JS jsx is visually less noisy and as such lets you grok the html structure more easily. Rescript jsx makes it super clear that you need a React.element inside tags, no magic....
View Article[ANN] Sunset of legacy build system
Nice! Will there be a CLI for it as well as editor integration?
View Article[ANN] Sunset of legacy build system
We’ve now switched to the new rescript build system and js-post-build works great FYI.
View ArticleClik here to view.
ReScript v12 js-post-build confusion
Works perfectly A few other things I had to contend with though: Yes the path is now absolute but it points to the file under lib/bs, before I think it was relative to the project root. The script you...
View ArticleEven more JSX customization
FYI: In my current custom implementation, generic components doesn’t work. Following code would throw an error. // Select.res type props<'a> = { options: array<'a>, getOptionId: 'a =>...
View ArticleReScript v12 js-post-build confusion
Thanks, this is useful feedback. Yes the path is now absolute but it points to the file under lib/bs, before I think it was relative to the project root. Yeah, the path under the project makes more...
View Article