Rescript frustration
There is this ticket that seems related to what you’re asking for: fill out the Option module? · Issue #85 · rescript-lang/rescript-core · GitHub
View ArticleHow you are dealing with sql in rescript?
Hi there. I’ve got a good opportunity to use rescript as a full-stack solution; the only missing thing is type-safe SQL or working ORM. There is no Prisma generator, so maybe some type-safe SQL...
View ArticleHow you are dealing with sql in rescript?
Shameless self plug, but I’ve built pgtyped-rescript (a ReScript fork of pgtyped) which I use in a lot of projects: pgtyped-rescript/RESCRIPT.md at rescript · zth/pgtyped-rescript · GitHub Let’s you...
View ArticleClik here to view.
How you are dealing with sql in rescript?
There are some things: [ANN] SQL query builder Hey, I’m not a big fan of orms, but unfortunately I have to use it in so many projects. So I started to write some typesafe query builders in typescript...
View ArticleClik here to view.
How you are dealing with sql in rescript?
fham: and I think @joshderochervlk had some prisma bindings? No, I have some other library bindings I’ve worked on but nothing in this space. @zth is the expert for these
View ArticleHow you are dealing with sql in rescript?
Because I needed to work with a range of databases and other folks in my team were sql devs, I used knex.js with custom bindings for an internal app. It let me use sql for querying and having ReScript...
View ArticleHow you are dealing with sql in rescript?
I’ve also thought about it. It looks like something easy to use and quite universal.
View ArticleClik here to view.
Problem with UltimateExpress bindings
I am trying to update existing bindings for express and move it to ultimate-express support (GitHub - dimdenGD/ultimate-express: The Ultimate Express. Fastest http server with full Express...
View ArticleProblem with UltimateExpress bindings
The compiler adds a $ and a number to an import when another import with the same name already exists. Is it really a problem?
View ArticleProblem with UltimateExpress bindings
I’ve to edit the post. Formatting has consumed part of the code. The issue is in “*”.
View ArticleProblem with UltimateExpress bindings
It looks like ultimate-express uses a default export, rather than exporting everything by name. One way to fix the bindings would be to use @send decorators on the default value. If you put something...
View ArticleClik here to view.
Problem with UltimateExpress bindings
(If you’re curious as to how I worked this out, this JS code tells the whole story. ) import * as UE from 'ultimate-express'; console.log(UE)
View ArticleProblem with UltimateExpress bindings
It seems that it needs to be called as a method on the default return of UltimateExpress. By wrapping it, you don’t have to pass around that value, but you could omit it if you wanted to.
View ArticleClik here to view.
Problem with UltimateExpress bindings
Ough. So, now I have to do it for every function. Is there a simpler way?
View ArticleRendering Recursive React Components
Hello! I have some questions about rendering recursive react components. See this small example: type rec item<'a> = { name: string, nested: option<item<'a>>, } module Item = {...
View ArticleRendering Recursive React Components
You can’t reference a module inside of itself, so you need to call the recursive make function instead. // before | Some(nested) => <Item item=nested /> // after | Some(nested) =>...
View ArticleClik here to view.
Rendering Recursive React Components
Brilliant, no need for React.createElement better!
View ArticleProblem with UltimateExpress bindings
Could write a shim in JS to do the remapping? Something like import UltimateExpress from "ultimate-express"; export const Router = UltimateExpress.Router; export const json = UltimateExpress.json .......
View ArticleRendering Recursive React Components
Just be careful; I don’t think you can have any hooks in a component that works this way.
View Article