feat: Add register command for auto-generating model registry#1
Merged
beesaferoot merged 2 commits intoJul 11, 2025
Merged
Conversation
Owner
|
Thanks for the PR @DivineUX23 will have a look |
beesaferoot
reviewed
Jul 11, 2025
beesaferoot
left a comment
Owner
There was a problem hiding this comment.
🪄 This is really cool. Thank you. 👍🏾
I added a few comments
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
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.
Description:
This pull request introduces a new register command to the migration tool. This feature significantly improves the user experience by automating the creation and maintenance of the models_registry.go file.
The Problem
Previously, users had to manually create the models_registry.go file and add every GORM model to the ModelTypeRegistry map. This process was tedious, error-prone, and difficult to keep in sync as a project's models evolved.
The Solution
The new register command solves this problem by:
This automation removes a manual step, reduces the chance of human error, and makes the tool much easier to adopt and use.
How to Use
To generate the model registry, a user can now simply run:
Key Changes
This change makes the initial setup and ongoing maintenance for users of this library much simpler and more robust.