Thank you for the post. It was interesting to read. I didn't get the I heard that exact object types are coming to Flow part. Isn't $Exact<{}> or {||} is an exact object type or am I missing something? It would be fair to notice that flow is written in ocaml which works threeish times faster when analysing a large project.
It's still an absurd thing to enforce as a compiler error, especially by default, and absolutely absurd for a tool based on Create-React-App.
Dan Abramov and I have both urged the author to change the default link setup (per create-react-app-ts #333 ). It looks like there's some open PRs to do that, but no recent progress. Very frustrating.
I actually just tried TS "for real" for the first time today, and I see some potential benefits to using it, but it's hard to recommend CRA-TS as a tool for a beginner with that ridiculously restrictive "lint" setup.
I like all ideas behind ML-family (OCaml, Elm etc), but the way it is currently done is not yet prefect. It is very promising, but requires a lot of work. This is short version
I have some eggs. I have to get only their yolks for my recipe. I may get them by hand. Or I could use a tool that does the job. But in this latter case I have to watch it ... maybe it can destroy some egg! Boh? Finally I decide to use my hands. Got it?
We're a place where coders share, stay up-to-date and grow their careers.
Thank you for the post. It was interesting to read. I didn't get the
I heard that exact object types are coming to Flowpart. Isn't $Exact<{}> or {||} is an exact object type or am I missing something? It would be fair to notice that flow is written in ocaml which works threeish times faster when analysing a large project.For those who already use flow in a app with redux this lib can come in pretty handy
github.com/lttb/typed-actions
I meant this post medium.com/flow-type/on-the-roadma...
"It asked me to sort properties alphabetically. Seriously who has time for this?"
You can use prettier-tslint to auto-fix many tslint errors.
It's still an absurd thing to enforce as a compiler error, especially by default, and absolutely absurd for a tool based on Create-React-App.
Dan Abramov and I have both urged the author to change the default link setup (per create-react-app-ts #333 ). It looks like there's some open PRs to do that, but no recent progress. Very frustrating.
I actually just tried TS "for real" for the first time today, and I see some potential benefits to using it, but it's hard to recommend CRA-TS as a tool for a beginner with that ridiculously restrictive "lint" setup.
Agreed, enforcing it as an error would be very frustrating especially for beginners.
Can't wait to try this github.com/facebook/create-react-a...
But can you write type-safe react routes with Flow? I don't think so. My vote goes to Typescript.
Reminds me old joke: how I would prefer code snippet
1) github repository
2) gist
3) blogpost
...
997) scanned screenshot in an email
998) written with blue paint on a cow
999) as a YouTube video
Nice write up :)
What about this "Don't get me started about ReasonML/BuckleScript" ?
I like all ideas behind ML-family (OCaml, Elm etc), but the way it is currently done is not yet prefect. It is very promising, but requires a lot of work. This is short version
I have some eggs. I have to get only their yolks for my recipe. I may get them by hand. Or I could use a tool that does the job. But in this latter case I have to watch it ... maybe it can destroy some egg! Boh? Finally I decide to use my hands. Got it?