Skip to content

feat(sidekick/rust): generate resource name with tracing and heuristics configs#4560

Merged
haphungw merged 13 commits intogoogleapis:mainfrom
haphungw:fix-tracing-path-template
Mar 13, 2026
Merged

feat(sidekick/rust): generate resource name with tracing and heuristics configs#4560
haphungw merged 13 commits intogoogleapis:mainfrom
haphungw:fix-tracing-path-template

Conversation

@haphungw
Copy link
Contributor

This PR groups together many PRs required for the Rust code generation, specifically ensuring that resource names and path templates are computed correctly when generating client libraries.

@codecov
Copy link

codecov bot commented Mar 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.35%. Comparing base (adbb644) to head (8523318).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4560   +/-   ##
=======================================
  Coverage   79.34%   79.35%           
=======================================
  Files         110      110           
  Lines        9181     9185    +4     
=======================================
+ Hits         7285     7289    +4     
  Misses       1387     1387           
  Partials      509      509           

☔ 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.

Copy link
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 introduces a significant and beneficial refactoring of the resource name generation logic for Rust clients, primarily for tracing purposes. The previous approach of finding candidate fields has been replaced with a more direct and simplified method that leverages the TargetResource. Additionally, the introduction of explicit type annotations in the Rust templates is a good step towards improving code clarity and maintainability. I have one minor suggestion to make a piece of the new Rust code more idiomatic.

@haphungw haphungw marked this pull request as ready for review March 13, 2026 11:55
@haphungw haphungw requested review from a team as code owners March 13, 2026 11:55
@haphungw haphungw force-pushed the fix-tracing-path-template branch from 8754c03 to 257f3bd Compare March 13, 2026 18:34
@haphungw haphungw requested a review from westarle March 13, 2026 22:24
Copy link
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 few minor (I hope changes).

@haphungw haphungw force-pushed the fix-tracing-path-template branch from 649a2ff to 58d0a25 Compare March 13, 2026 22:47
Copy link
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.

Please fix the other Has* field you are introducing and then merge.

@haphungw haphungw force-pushed the fix-tracing-path-template branch from c108326 to 8523318 Compare March 13, 2026 23:42
@haphungw haphungw merged commit e9fbad6 into googleapis:main Mar 13, 2026
18 checks passed
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.

3 participants