-
Notifications
You must be signed in to change notification settings - Fork 9
feat(modfile): add run directive support for custom project runners #125
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
base: main
Are you sure you want to change the base?
Conversation
Add support for 'run' directive in gop.mod/gox.mod files that allows specifying a custom runner command for projects. This enables projects like SPX to define their own run command: run github.com/goplus/spx/v2/cmd/spxrun Changes: - Add Run struct type to hold the custom runner package path - Add Run field to File struct - Add parsing logic for 'run' directive in parseVerb function
Summary of ChangesHello @joeykchen, 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 enhances the module file parsing by adding a new 'run' directive. This directive allows projects to define and utilize custom commands for execution, providing greater flexibility in how projects are run. The change involves updating the core data structures to accommodate this new configuration and implementing the necessary parsing logic to interpret the directive correctly. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. 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
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #125 +/- ##
==========================================
- Coverage 93.37% 91.60% -1.77%
==========================================
Files 6 6
Lines 679 691 +12
==========================================
- Hits 634 633 -1
- Misses 27 40 +13
Partials 18 18 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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 run directive to gop.mod/gox.mod files, allowing projects to specify a custom runner. The implementation is solid, adding a new Run struct, updating the File struct, and including parsing logic in parseVerb. My main feedback is to rename the Cmd field in the Run struct to Path for better consistency and clarity, as it stores a package path, not an executable command string.
| // A Run is the run statement that specifies a custom runner for the project. | ||
| // Example: run github.com/goplus/spx/v2/cmd/spxrun | ||
| type Run struct { | ||
| Cmd string // the command package path to run the project |
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.
For consistency with other structs in this file like Import that use Path for package paths, and to more accurately reflect that this field holds a package path rather than a command string, consider renaming Cmd to Path. This would improve code clarity and maintainability.
| Cmd string // the command package path to run the project | |
| Path string // the package path of the custom runner command |
| wrapError(err) | ||
| return | ||
| } | ||
| f.Run = &Run{Cmd: cmdPath, Syntax: line} |
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.
| } | ||
|
|
||
| // A Run is the run statement that specifies a custom runner for the project. | ||
| // Example: run github.com/goplus/spx/v2/cmd/spxrun |
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.
Documentation Issue: The example comment appears to have a formatting error. It should use // for the comment prefix to be consistent with Go documentation standards.
| // Example: run github.com/goplus/spx/v2/cmd/spxrun | |
| // A Run is the run statement that specifies a custom runner for the project. | |
| // Example: run github.com/goplus/spx/v2/cmd/spxrun |
| // A Run is the run statement that specifies a custom runner for the project. | ||
| // Example: run github.com/goplus/spx/v2/cmd/spxrun | ||
| type Run struct { | ||
| Cmd string // the command package path to run the project |
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.
Clarity Improvement: The term "command package path" could be clearer. Consider specifying that this is a Go package import path.
| Cmd string // the command package path to run the project | |
| Cmd string // Go package import path of the custom runner command |
| XGo *XGo | ||
| Compiler *Compiler // the underlying go compiler in go.mod (not gox.mod) | ||
| Projects []*Project | ||
| Run *Run // custom runner command |
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.
Optional - Field Ordering: Consider grouping file-level configuration directives (XGo, Compiler, Run) together, separate from collection fields (Projects, ClassMods). This would improve logical organization:
| Run *Run // custom runner command | |
| Run *Run // custom runner for executing the project (from run directive) |
And move it to line 45 (after Compiler, before Projects).
| return | ||
| } | ||
| if len(args) != 1 { | ||
| errorf("usage: run cmdPkgPath") |
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.
Minor - Error Message: Consider making the usage message clearer by showing a concrete example format:
| errorf("usage: run cmdPkgPath") | |
| errorf("usage: run <package-import-path>") |
Or: "usage: run github.com/org/project/cmd/runner"
Review SummarySolid implementation that follows existing codebase patterns well. The Key findings:
Main action item: Fix comment formatting on line 36. Consider adding test cases following patterns in |
Add support for 'run' directive in gop.mod/gox.mod files that allows specifying a custom runner command for projects. This enables projects like SPX to define their own run command:
run github.com/goplus/spx/v2/cmd/spxrun
Changes: