refactor(cmd/gf): use automatic generating package names for go files of dao/do/entity instead of constant package names
#3639
Conversation
This file contains 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
gqcn
requested changes
Jun 12, 2024
gqcn
approved these changes
Jun 13, 2024
gqcn
changed the title
dao/do/entity instead of constant package names
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When employing the CLI to instantiate the generation of dao, one customarily specifies parameters such as daoPath, doPath, and entityPath. These parameters determine the file paths for the generated Go files, while the package names default to dao, do, and entity. To address this, an additional configuration parameter, withPathPackage, has been introduced. If withPathPackage is set to true, the package names will be defined according to the respective paths specified by daoPath, doPath, and entityPath.