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

What could go wrong if not using uppercase in route names? #46

Open
ddanielcruzz opened this issue Nov 29, 2023 · 1 comment
Open

What could go wrong if not using uppercase in route names? #46

ddanielcruzz opened this issue Nov 29, 2023 · 1 comment

Comments

@ddanielcruzz
Copy link

Hey, great library!

I saw the in the docs that mention the following:

❗Child routes have to start with an uppercase letter to prevent overlapping with route API.

I was wondering if you could go more in detail of what this means, as I like my routes in lowercase haha.

Thanks!

@fenok
Copy link
Owner

fenok commented Nov 29, 2023

Hi, thanks!

I wanted to ensure that the future route APIs wouldn't clash with someone's child routes. Using an uppercase letter also clearly indicates that it's a child route.

I've actually come to regret the decision to force child routes to start with an uppercase letter. The next major release will allow basically any naming scheme for child routes because route APIs will be prefixed with a $ (at least it's the current plan). It's like 90% done, I just need to refactor the code a bit and document everything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants