[ANN] ergonomic MSW bindings for testing graphql-ppx operations
I’ve published an update 0.2.0 for compatibility with MSW 2. The API changes in MSW remove the need for the pipe-able wrapper I created for the initial release; the output is nearly zero-cost now and...
View Article[ANN] ergonomic MSW bindings for testing graphql-ppx operations
Would be awesome if you had a look at supporting relay as well! Nothing else exists, that I know of at least.
View ArticleClik here to view.
Tilia is born... still early version, ideas welcome :-)
hope this clarifies it a little Absolutely! So the fine-grained reactivity is achieved via observing access to properties, so a potentially large tree can be subscribed many times via Tilia.use and...
View ArticleRFC: Nested record definitions
Today, if you want to have nested records, you need to define each record as a distinct type, in the correct order, and plug them together. An example: type persistOptionsFileConfig = { extension?:...
View ArticleRFC: Nested record definitions
+1 I have already wanted this more than once. In your options example, would you be able to create or reference any of the nested types by themselves, or would they always need to be a part of option?...
View ArticleRFC: Nested record definitions
They’d work by themselves, they’ll be an actual defined type to the compiler. It’s just that (in this proposal as of now) referring to them by typename can’t be done without using escaped identifiers,...
View ArticleRFC: Nested record definitions
I’ve had the need for this quite often when writing bindings!
View Article"recursion" in a function argument via callback
I have a function, that returns another function, say let registerSW = (opts) => () => () the return type of the registerWS is a function to update service worker, let’s call it updateSW. In the...
View ArticleClik here to view.
"recursion" in a function argument via callback
Can you give the full example of what you are trying to do? Is just the registerSW function external or updateSW as well? You are not using any external keyword here. If the signature of “registerSW”...
View ArticleClik here to view.
"recursion" in a function argument via callback
fham: Is just the registerSW function external or updateSW as well? The updateSW is a return of the registerSW, so it is intrinsically external as the registerSW is external. I’m loading it from the...
View ArticleClik here to view.
"recursion" in a function argument via callback
Now I get it, your problem is not really recursion itself but immutability. You can do it with a ref. type opts = {foo: React.element} @val external registerSW: opts => unit => unit =...
View ArticleCome work with us at Walnut in the one of the largest ReScript codebases...
At Walnut we have two (!) open positions as a software engineer. We have a > 500kloc ReScript codebase. With Walnut’s capturing technology and WYSIWYG editor, it’s possible to create stand-alone...
View Article"recursion" in a function argument via callback
That helps, thanks! I did not suspected an immutability to be a problem, since I never reassigned the let updateSW. I suspected the type system to be a cause, as it encountered a cycle while resolving...
View ArticleClik here to view.
"recursion" in a function argument via callback
So ignore has the following signature: 'a => unit, it will only work for functions that have one arbitrary parameter and return unit. In your case, updateSW has the signature unit => unit which...
View ArticleWhen @tag is provided, constructor without payload still compiles to string...
Empty inline records now work too.
View ArticleI'm working on some bindings for a Remix app and I could use some help with a...
Would you be happy to share where you got to on your bindings so far? (Remix or react router v7? )Thx
View ArticleReScript React Docs Busted
Are the ReScript React docs busted (showing a blank page) for everyone else? I opened a GitHub issue on the ReScript React repository, but I’m unsure if that’s the correct place to report it.
View Article