Skip to content

Adopt Snake Case Naming for Route Paths and Names #20318

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

Merged

Conversation

ahmed-bhs
Copy link
Contributor

Hey everyone,

I’ve got a quick idea I’d love to share: let’s embrace snake_case for our routing in Symfony and make sure it’s included in the contribution docs.

1. RFC Compliance

First off, the RFC 3986 gives us the thumbs up for clear naming conventions. snake_case does just that—it's super readable and fits the bill perfectly.

2. Practices of Other Languages

Plus, many languages like Python and Ruby are already on the snake_case train. This makes it way easier for developers coming from other backgrounds.

3. Industry Practices

And hey, check this out: major players like Google, Facebook, and Twitter use snake_case in their APIs. If it’s good enough for them, it’s definitely worth considering!
Conclusion

By adopting snake_case for route names and paths and adding this to our contribution docs, we’ll boost the consistency and clarity of Symfony.

@OskarStark OskarStark changed the base branch from 7.1 to 5.4 October 14, 2024 06:05
@OskarStark OskarStark force-pushed the docs/snake-case-routing-guidelines branch from 04ff5ac to 5bb2654 Compare October 14, 2024 06:05
@OskarStark
Copy link
Contributor

Thank you @ahmed-bhs.

@OskarStark OskarStark merged commit 0fb2ba4 into symfony:5.4 Oct 14, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants