fixed migration name into camel case #66
Open
+66
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
coolwednesday
requested changes
Nov 7, 2025
Member
coolwednesday
left a comment
coolwednesday
left a comment
There was a problem hiding this comment.
In Go, file names use all lowercase with optional underscores (e.g., user_service.go), while function names use camelCase for unexported and PascalCase for exported ones (e.g., getUser(), GetUser()).
Capitalization in Go determines visibility — uppercase = exported, lowercase = package-private.
Currently both go to CamelCase. Can you check and fix this. ( we need exported so pascalcase needs to be used )
Member
|
@thzgajendra Are you still working on this PR? If yes, can you please resolve the review comment given above. Thankyou |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes : gofr-dev/gofr#2438