Skip to content

Conversation

@fmeum
Copy link
Collaborator

@fmeum fmeum commented Dec 5, 2025

RELNOTES: By comparing tag objects, module extensions can check which one preceded the other within a module file and/or in BFS module order, even across tag classes. This allows them to determine precedence based on order when tags from multiple tag classes interact.

Context: https://github.com/bazel-contrib/rules_go/pull/4526/files#r2586719526

@fmeum
Copy link
Collaborator Author

fmeum commented Dec 5, 2025

@bazel-io fork 9.0.0

@github-actions github-actions bot added team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. awaiting-review PR is awaiting review from an assigned reviewer labels Dec 5, 2025
@gemini-code-assist
Copy link

Summary of Changes

Hello @fmeum, 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 introduces a significant enhancement to module extensions by enabling the comparison of tag objects. This functionality allows module extensions to programmatically understand the relative ordering of tags, which is crucial for implementing logic that depends on the sequence in which tags are defined. The change provides module extension authors with greater control and flexibility in how they process and interpret tag configurations.

Highlights

  • Module Extension Tag Comparison: Module extension tags can now be compared, allowing module extensions to determine the relative order of tags, even across different tag classes.
  • Precedence Based on Order: This new comparison capability enables module extensions to establish precedence among tags based on their definition order within a module file and across modules in BFS order.
  • Internal Implementation Changes: The TypeCheckedTag class now implements Comparable and includes a compareKey derived from the module and tag indices to facilitate ordered comparison.
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 introduces the ability to compare module extension tags, which is a great feature for determining precedence. The implementation is solid: TypeCheckedTag now implements Comparable, using a cleverly constructed compareKey from module and tag indices to ensure a correct and efficient sort order. The new tests are thorough, covering both unit-level comparisons and an end-to-end scenario with multiple modules and tag classes. The switch to LinkedHashMap for storing tags is also a nice touch for improving determinism.

I've found one area for improvement regarding the Comparable contract, which I've detailed in a specific comment.

RELNOTES: By comparing tag objects, module extensions can check which one preceded the other within a module file and/or in BFS module order, even across tag classes. This allows them to determine precedence based on order when tags from different tag classes are specified.
@fmeum
Copy link
Collaborator Author

fmeum commented Dec 5, 2025

@bazel-io fork 8.5.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-review PR is awaiting review from an assigned reviewer team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant