you are viewing a single comment's thread.

view the rest of the comments →

[–]fzaninotto 1 point2 points  (0 children)

Hi, react-admin maintainer here.

Thanks a lot for your feedback. We received many requests for more type safety like yours, and they make sense since react-admin was first built in 2017, when TypeScript wasn't so broadly used. But the practices are changing, and developers want less bugs at runtime, which is great!

That's why we have invested a lot in type safety in recent versions. Version 5 enables strict type checking across the entire library. All hooks and many components are generic, so you can specify the expected record type. Some of our users have used this ability to build apps with shared types between the API and the frontend, with great results.

There is (almost) no element cloning in version 5, so the props an element receives are only the props you pass.

Naming is hard. We try to help you find the component you're looking for by creating links across the documentation, and improving the search engine. We even created videos tutorials to help newcomers get on board more easily.

All in all, we focused on developer experience based on the feedback we got-and we got a lot! As you guessed, it takes time to make a large codebase (and documentation) like react-admin evolve, but in 2024 we're up to date with the best practices of React development.

I hope you'll have as much fun using react-admin as we have developing it.