Skip to content
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

feat: route level typesafety #1754

Open
adex-codez opened this issue Feb 2, 2024 · 1 comment
Open

feat: route level typesafety #1754

adex-codez opened this issue Feb 2, 2024 · 1 comment
Labels
🌟 enhancement New feature or request

Comments

@adex-codez
Copy link

adex-codez commented Feb 2, 2024

Is your feature request related to a problem? Please describe.

This is not really a problem but I would like to see this implemented because it would give us autocomplete capabilities, reduce runtime errors because a URL given is not found and I also think it would fit into the type safety capability the create-t3-app provides

Describe the solution you'd like to see

The solution I would like to see is adding the next-typesafe-url package and giving the options to use it or not

Describe alternate solutions

Implementing route level typesafety

Additional information

No response

@adex-codez adex-codez added the 🌟 enhancement New feature or request label Feb 2, 2024
@raymondkneipp
Copy link

I have been using typedRoutes - https://nextjs.org/docs/app/api-reference/next-config-js/typedRoutes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌟 enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants