You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found the naming of the ToCamel function a bit confusing when I first reviewed the code in camel_test.go. Initially, I thought it might be a typo in the source code. However, as I continued, I came across the ToLowerCamel function, which clarified that the naming was intentional.
I’m raising this issue because:
If this library is used in a project, other developers might get confused when they encounter the ToCamel function. This confusion could lead to misunderstandings, especially during code reviews.
Most developers associate the naming convention with PascalCase, making the current name inconsistent with common expectations.
Naming the function ToCamel may reduce code readability, as its purpose isn’t immediately clear without a deeper dive into the library, particularly the ToLowerCamel method.
This is a fantastic library, but I believe addressing this naming issue would make it even better. Could this be reconsidered and updated?
The text was updated successfully, but these errors were encountered:
I found the naming of the ToCamel function a bit confusing when I first reviewed the code in camel_test.go. Initially, I thought it might be a typo in the source code. However, as I continued, I came across the ToLowerCamel function, which clarified that the naming was intentional.
I’m raising this issue because:
This is a fantastic library, but I believe addressing this naming issue would make it even better. Could this be reconsidered and updated?
The text was updated successfully, but these errors were encountered: