Skip to content

feat(sidekick): Relax AIP checks for samples of delete operations#3519

Merged
amanda-tarafa merged 1 commit intogoogleapis:mainfrom
amanda-tarafa:relax-aips-for-delete-samples
Jan 12, 2026
Merged

feat(sidekick): Relax AIP checks for samples of delete operations#3519
amanda-tarafa merged 1 commit intogoogleapis:mainfrom
amanda-tarafa:relax-aips-for-delete-samples

Conversation

@amanda-tarafa
Copy link
Copy Markdown
Contributor

Not all resources define a singular name so we can't rely on that only. We now also look at fields named name with no-singular resource.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @amanda-tarafa, 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 flexibility of AIP-135 compliance checks for delete operations within the sidekick component. It addresses scenarios where resources may not define a singular name by adjusting the logic to prioritize fields explicitly named 'name' when identifying the resource name field. This change ensures that the system can correctly identify and process delete operations for a broader range of resource definitions, improving robustness without compromising the core intent of the AIP standards.

Highlights

  • Relaxed AIP-135 Delete Checks: The logic for identifying the resource name field in AIP-135 compliant delete operations has been made more flexible to accommodate resources without a singular name.
  • Prioritized Field Matching: A new prioritization scheme is introduced to find the ResourceNameRequestField for delete operations. It now favors fields explicitly named 'name' even if the associated resource lacks a singular name, and then falls back to fields matching the resource's singular name.
  • Updated Documentation: Comments for AIPStandardGetInfo and AIPStandardDeleteInfo have been updated to clarify that these operations are 'like' those defined by AIP-131/135, rather than strictly 'as defined by', reflecting the broader interpretation.
  • Comprehensive Test Coverage: New test cases have been added to thoroughly validate the updated field matching logic, covering scenarios with missing singular names and different field naming priorities to ensure robustness.

🧠 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 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
Copy Markdown
Contributor

@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 relaxes the checks for what is considered a standard AIP delete operation. It now also considers fields named name for resources without a singular name, which makes the check more flexible. The logic for finding the resource name field is updated with a clear prioritization, and this is well-supported by new test cases. The changes are solid, I just have one minor suggestion to fix a typo in a comment.

@codecov
Copy link
Copy Markdown

codecov bot commented Jan 10, 2026

Codecov Report

❌ Patch coverage is 92.30769% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 81.04%. Comparing base (cc3ee38) to head (2263b99).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
internal/sidekick/api/model.go 92.30% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3519   +/-   ##
=======================================
  Coverage   81.03%   81.04%           
=======================================
  Files         166      166           
  Lines       13775    13782    +7     
=======================================
+ Hits        11163    11170    +7     
  Misses       2032     2032           
  Partials      580      580           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Not all resources define a singular name so we can't rely on that only. We now also look at fields named `name` with no-singular resource.
@amanda-tarafa
Copy link
Copy Markdown
Contributor Author

This is ready for review, latest counterpart in googleapis/google-cloud-rust#4245.

@amanda-tarafa amanda-tarafa marked this pull request as ready for review January 11, 2026 22:48
@amanda-tarafa amanda-tarafa requested a review from a team January 11, 2026 22:48
Copy link
Copy Markdown
Contributor

@coryan coryan left a comment

Choose a reason for hiding this comment

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

A small comment nit, feel free to merge and then fix in a follow-up PR.

@amanda-tarafa amanda-tarafa merged commit adf34df into googleapis:main Jan 12, 2026
10 of 11 checks passed
@amanda-tarafa amanda-tarafa deleted the relax-aips-for-delete-samples branch January 12, 2026 00:45
amanda-tarafa added a commit to googleapis/google-cloud-rust that referenced this pull request Jan 12, 2026
This includes the baseline sample for all simple RPCs (non-LRO and
non-paginated) plus specific samples for get and non-LRO deletes.
Its latest counterpart is
googleapis/librarian#3519

Best to review one commit at a time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants