-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how-to-keep-your-remix-routes-tidy #8
Comments
Thanks for a great article. Would you be open to share how you structure your API calls and export the type definitions in your feature files? Would love to see your take. |
Hey @drewes! Thanks for your comment! In fact, the source code of the blog is open, and we are constantly improving it. Just check https://github.com/remix-cookbook/remix-cookbook.com and use it in any way you see fit. I'm curious about your opinion. 👋🏻 |
Thanks for sharing! I like the idea but as far as the JSX abstraction, if we have to open another file to edit our JSX we loose one of remix greatest strengths : code colocation |
@gustavoguichard Hey Gustavo! Thanks for the comment. Rest assured your point of view is welcome! I personally believe colocation is great but for everything else but the view. The main point of the article is to let people know it is not required to keep everything in the route. Take care! |
Hey @vedovelli, thanks for the reply! Sure... great article btw. |
@gustavoguichard I am curious about your concerns. React is all about components and composability. Smaller components working together means they're easier to reason about and to be tested. Even Remix favors this approach with nested routes. I am not trying to prove you wrong, far from that. I just want to make sure we are in the same page here! 👋🏻 |
Remix Cookbook - How to keep your Remix routes tidy
Remix is a server-side framework which makes use of React as the view layer. Newcomers could face some well-known challenges while building server-...
https://remix-cookbook.com/how-to-keep-your-remix-routes-tidy
The text was updated successfully, but these errors were encountered: