-
Couldn't load subscription status.
- Fork 71
Shareable Go package experiment in sdk-platform-java #3938
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
langaugecontainer and message packages are to be migrated to the librarian repository.
Summary of ChangesHello @suztomo, 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 initiates an experimental refactoring effort to modularize the 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 refactors the command-line handling into a shared languagecontainer package, which is a good step towards modularity. However, there are a few critical issues that need to be addressed. The new implementation incorrectly passes os.Args to the Run function, which will cause command dispatching to fail. I've also pointed out that error handling has been changed to use panic, which is not ideal for a CLI tool and should be reverted to graceful error logging and exit codes. Additionally, the --version flag functionality has been lost in the refactoring. My review includes suggestions to fix these issues.
| slog.Info("librariangen: finished successfully") | ||
| return 0 | ||
| container := javaContainer{} | ||
| os.Exit(languagecontainer.Run(os.Args, &container)) |
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.
The Run function in languagecontainer expects the command-line arguments without the program name. Currently, os.Args is passed, which includes the program name as the first element (os.Args[0]). This will cause the command dispatching in Run to fail, as it will try to match the program name against commands like generate. You should pass os.Args[1:] instead.
| os.Exit(languagecontainer.Run(os.Args, &container)) | |
| os.Exit(languagecontainer.Run(os.Args[1:], &container)) |
| if len(args) < 1 { | ||
| panic("args must not be empty") | ||
| } |
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.
| if err != nil { | ||
| // TODO: Save it as a response file. | ||
| panic(err) | ||
| } |
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.
Using panic for handling errors from business logic can lead to abrupt program termination, which is generally undesirable for a CLI tool. It's better to log the error and return a non-zero exit code to indicate failure gracefully.
if err != nil {
// TODO: Save it as a response file.
slog.Error("librariangen: generate command failed", "error", err)
return 1
}| if err != nil { | ||
| panic(err) | ||
| } |
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.
Using panic for handling errors can lead to abrupt program termination. It's better to log the error and return a non-zero exit code to indicate failure gracefully, which is more conventional for CLI applications.
if err != nil {
slog.Error("librariangen: configure command failed", "error", err)
return 1
}| slog.Error("librariangen: unknown command: %s (with flags %v)", args[0], args) | ||
| return 1 | ||
| } | ||
| return 0 |
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.
|
|
||
| // run executes the appropriate command based on the CLI's invocation arguments. | ||
| // The idiomatic structure is `librariangen [command] [flags]`. | ||
| func run(ctx context.Context, args []string) error { |
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.
|
|



langaugecontainer and message packages are to be migrated to
the librarian repository.
Thank you for opening a Pull Request! Before submitting your PR, please read our contributing guidelines.
There are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> ☕️