6 ms·
It really should have Typescript as well (optionally, that is)
by anarchy8 5y ago
It really should have Typescript as well (optionally, that is)
- kall 5y agoI think the way the docs introduce functional components (destructure the props argument right away) sets you up for success with TypeScript. The main ways to get started that they recommend (CodeSandbox, CRA, next.js) let you add typescript down the line with no hassle, so you don't loose out by starting without it. Seems better to teach people one thing at a time. React with TypeScript really doesn't look all that different and if you just drop what they teach you into an existing TS project, it will work ok. An official "Using React with Typescript" doc that shows good patterns for typing props and state would be nice though.
- acemarke 5y agoThe de-facto standard resource on React + TS is the community-maintained React TypeScript Cheatsheet site: https://react-typescript-cheatsheet.netlify.app/ https://react-typescript-cheatsheet.netlify.app/ But yes, I'd love to have some of this info added to the official docs as well.
- danabramov 5y agoYeah we’d like to add something (potentially even toggles) but out of scope for the first iteration.
- acemarke 5y agoSweet! As an FYI for later reference, Lenz Weber has a Remark plugin that compiles TS to JS in code samples - we use that in the Redux Toolkit docs. I think Orta Therox may have something similar going on with his "Shiki Twoslash" tooling, but not entirely sure.
- TameAntelope 5y agoWell, this is Typescript, isn't it?
- _fat_santa 5y agoThat would be amazing. I would love it if they put together a guide to proper typechecking around hooks.
- dagurp 5y agoIt flow since it's from FB as well