Skip to content

Conversation

@suztomo
Copy link
Member

@suztomo suztomo commented Oct 14, 2025

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:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> ☕️

langaugecontainer and message packages are to be migrated to
the librarian repository.
@product-auto-label product-auto-label bot added the size: m Pull request size is medium. label Oct 14, 2025
@gemini-code-assist
Copy link

Summary of Changes

Hello @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 sdk-platform-java project. It introduces two new Go packages, languagecontainer and message, designed to be language-agnostic and eventually shared across different language platforms via a librarian repository. The languagecontainer package defines a core interface for language-specific operations and a generic command execution mechanism, while the message package provides standardized data structures for inter-module communication. The main CLI entry point has been updated to integrate with this new architecture, showcasing how Java-specific logic will plug into the generic container framework.

Highlights

  • Introduced languagecontainer package: A new package defining a generic LanguageContainer interface with Generate and Configure methods, along with a Run function to dispatch commands based on command-line arguments.
  • Created message package: A new package for defining common request and response data structures (GenerateRequest, ConfigureRequest, etc.) used for communication between the CLI and language containers.
  • Refactored main.go: The main CLI entry point was updated to utilize the new languagecontainer.Run function, demonstrating how a language-specific implementation (javaContainer) will interact with the generic command dispatcher, replacing the previous command parsing logic.
  • Prepared for module migration: The newly introduced languagecontainer and message packages are explicitly marked for future migration to a shared librarian repository, indicating a strategic move towards a more modular and reusable architecture.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a 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))

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

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.

Suggested change
os.Exit(languagecontainer.Run(os.Args, &container))
os.Exit(languagecontainer.Run(os.Args[1:], &container))

Comment on lines +62 to +64
if len(args) < 1 {
panic("args must not be empty")
}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Panicking on invalid user input (like missing arguments) is ungraceful for a command-line tool. It's better to print an error message and exit with a non-zero status code. This provides a better user experience.

	if len(args) < 1 {
		slog.Error("librariangen: expected a command")
		return 1
	}

Comment on lines +69 to +72
if err != nil {
// TODO: Save it as a response file.
panic(err)
}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

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
		}

Comment on lines +77 to +79
if err != nil {
panic(err)
}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This return 0 statement is unreachable because all paths in the preceding switch statement return a value. This line can be removed.


// 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 {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The removed run function handled the --version flag. This logic has not been moved to the new implementation, which is a regression. The --version flag handling should be added back, likely in the main function before calling languagecontainer.Run.

@sonarqubecloud
Copy link

@sonarqubecloud
Copy link

Quality Gate Passed Quality Gate passed for 'java_showcase_integration_tests'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@suztomo suztomo changed the title Shareed module experiment in sdk-platform-java Sharable module experiment in sdk-platform-java Oct 14, 2025
@suztomo suztomo changed the title Sharable module experiment in sdk-platform-java Shareable Go package experiment in sdk-platform-java Oct 14, 2025
@suztomo suztomo marked this pull request as draft October 20, 2025 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size: m Pull request size is medium.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant