-
Notifications
You must be signed in to change notification settings - Fork 45
Optimize registry #441
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
Optimize registry #441
Conversation
Summary of ChangesHello @hiyuchang, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly refactors the module registration system, moving from a decorator-based approach to a centralized, explicit mapping within Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a significant and beneficial refactoring of the registry system, moving from a decorator-based approach to a centralized mapping scheme. This greatly improves maintainability and helps prevent circular import issues. The addition of comprehensive registry tests is also a valuable contribution. I've found one critical issue related to a circular import in the trinity/buffer/storage module, which I've detailed in the comments. Once that is addressed, this PR will be in great shape.
|
/unittest-all |
Summary
Tests
Github Test Reporter by CTRF 💚 |
|
/unittest-all |
Summary
Skipped
Tests
Github Test Reporter by CTRF 💚 |
|
/gemini review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a significant and beneficial refactoring of the module registration system. It moves from a decorator-based approach to a centralized mapping within __init__.py files for each registry. This improves code organization, reduces import side-effects, and makes the registration process more explicit and easier to track. The changes are consistently applied across the entire codebase, including the core library, examples, and documentation. A comprehensive new test suite for the registry functionality has also been added, which is excellent. I've found a couple of minor typos in the documentation and test files, which I've commented on. Overall, this is a high-quality pull request that improves the maintainability of the framework.
|
/unittest-all |
Summary
Skipped
Tests
Github Test Reporter by CTRF 💚 |
Description
@WORKFLOWS.register("math_boxed_workflow"), use the mapping scheme instead. Fix theimportaccordinglyChecklist
Please check the following items before code is ready to be reviewed.