Skip to content

🧹 chore: Add iterator helpers for client types #3560

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

Merged
merged 2 commits into from
Jul 2, 2025

Conversation

ReneWerner87
Copy link
Member

@ReneWerner87 ReneWerner87 commented Jul 1, 2025

Summary

  • add All iterators for Cookie and PathParam
  • deprecate VisitAll and delegate to the new iterators
  • update hooks to use the new APIs
  • document iterator usage in the client docs

@Copilot Copilot AI review requested due to automatic review settings July 1, 2025 12:36
@ReneWerner87 ReneWerner87 requested a review from a team as a code owner July 1, 2025 12:36
@ReneWerner87 ReneWerner87 requested review from gaby, sixcolors and efectn July 1, 2025 12:36
Copy link
Contributor

coderabbitai bot commented Jul 1, 2025

Walkthrough

This change replaces the callback-based VisitAll methods on Cookie and PathParam types with new All() iterator methods returning an iterator function. Corresponding code and documentation are updated to use for loops over All(). The old VisitAll methods are removed, and iteration logic in hooks and examples is adjusted accordingly.

Changes

File(s) Change Summary
client/request.go Removed VisitAll methods; added All() iterator methods for Cookie and PathParam.
client/hooks.go Replaced all VisitAll usage with for loops iterating over All() iterator results.
docs/client/request.md Updated documentation to replace VisitAll with All() methods and describe iterator usage.
docs/client/hooks.md Changed example code to use for loops over All() instead of VisitAll callbacks.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Client
    participant Cookie/PathParam

    User->>Client: Call All() on Cookie/PathParam
    Client->>Cookie/PathParam: All() returns iterator
    loop For each key, val in All()
        Client->>Client: Process key, val
    end
Loading

Possibly related PRs

Suggested labels

✏️ Feature

Suggested reviewers

  • sixcolors
  • gaby

Poem

A rabbit hopped through fields of code,
Where VisitAll once took the road.
Now All() leads with loops anew,
Simpler steps for tasks to do.
Cookies, paths—just iterate,
And let the old ways deprecate!
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2411bc4 and 055400d.

📒 Files selected for processing (2)
  • client/request.go (2 hunks)
  • docs/client/request.md (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • docs/client/request.md
  • client/request.go
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: unit (1.24.x, windows-latest)
  • GitHub Check: repeated
  • GitHub Check: Compare
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@ReneWerner87 ReneWerner87 requested a review from ksw2000 July 1, 2025 12:36
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR introduces new iterator helpers for client types by adding All iterators for Cookie and PathParam, deprecating the VisitAll methods, and updating hooks and documentation to use the new APIs.

  • Introduces All() iterators that yield key-value pairs for Cookie and PathParam types.
  • Deprecates the VisitAll functions in favor of the new iterator-based approach.
  • Updates client docs and hooks to reflect the new APIs.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
docs/client/request.md Adds documentation for the new All iterators on Cookie and PathParam.
docs/client/hooks.md Updates example code to use All() iterators instead of VisitAll.
client/request.go Implements new All() iterators and deprecates VisitAll for Cookie and PathParam.
client/hooks.go Refactors header, cookie, and path parameter iteration to use All() iterators.
Comments suppressed due to low confidence (3)

docs/client/request.md:1210

  • Clarify in the documentation that the keys and values returned by All() should not be stored beyond the loop’s scope to prevent unintended side effects.
**All** returns an iterator over all cookies. The key and value returned

client/request.go:775

  • Consider adding a brief inline comment to explain that returning false from yield will terminate the iteration, which can help maintainers understand this control flow decision.
			if !yield(k, v) {

client/hooks.go:74

  • [nitpick] Ensure consistent formatting and indentation for the new iteration loops across the codebase to enhance readability.
	for key, val := range req.path.All() {

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.

Summary of Changes

Hello @ReneWerner87, 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 modernizes the iteration patterns for Cookie and PathParam types within the client library by introducing new All() methods that return Go 1.22+ iterator sequences. This change aims to provide a more idiomatic and potentially more efficient way to access key-value pairs, while gracefully deprecating the older VisitAll() methods. The update also includes necessary adjustments to internal code that consumes these types and comprehensive documentation updates to guide users on the new API.

Highlights

  • New Iterator Methods: Introduced new All() iterator methods for Cookie and PathParam types. These methods return iter.Seq2[string, string], leveraging Go's new iterator functionality to provide a more idiomatic way to iterate over key-value pairs.
  • Deprecation and Delegation: The existing VisitAll() methods on Cookie and PathParam types have been deprecated. Their implementations now delegate to the newly introduced All() iterators, ensuring backward compatibility while encouraging adoption of the new API.
  • Internal Code Updates: Internal client hooks in client/hooks.go have been updated to utilize the new All() iterators for processing path parameters and cookies, replacing direct calls to the deprecated VisitAll() methods.
  • Documentation Updates: The client documentation has been updated to reflect these changes. This includes adding detailed documentation for the new All() methods in docs/client/request.md and updating an example in docs/client/hooks.md to demonstrate the use of All() for iterating over response headers.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.

@ReneWerner87
Copy link
Member Author

should we remove the VisitorAll function ?

@ReneWerner87 ReneWerner87 added this to v3 Jul 1, 2025
@ReneWerner87 ReneWerner87 added this to the v3 milestone Jul 1, 2025
Copy link

codecov bot commented Jul 1, 2025

Codecov Report

Attention: Patch coverage is 77.77778% with 4 lines in your changes missing coverage. Please review.

Project coverage is 90.93%. Comparing base (dd73968) to head (055400d).
Report is 2 commits behind head on main.

Files with missing lines Patch % Lines
client/request.go 60.00% 2 Missing and 2 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3560      +/-   ##
==========================================
- Coverage   90.97%   90.93%   -0.04%     
==========================================
  Files         110      110              
  Lines       11064    11066       +2     
==========================================
- Hits        10065    10063       -2     
- Misses        745      747       +2     
- Partials      254      256       +2     
Flag Coverage Δ
unittests 90.93% <77.77%> (-0.04%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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 idiomatic iterators for Cookie and PathParam types, which improves the client API. I've identified a potential performance improvement in the URL parsing hook, some leftover comments, and an incorrect code example in the documentation.

@ReneWerner87 ReneWerner87 requested a review from ksw2000 July 2, 2025 06:44
@ReneWerner87
Copy link
Member Author

@ksw2000 check again

@gaby gaby moved this to In Progress in v3 Jul 2, 2025
@gaby gaby changed the title Add iterator helpers for client types 🧹 chore: Add iterator helpers for client types Jul 2, 2025
@ReneWerner87 ReneWerner87 merged commit e041d63 into main Jul 2, 2025
13 of 14 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in v3 Jul 2, 2025
@ReneWerner87 ReneWerner87 deleted the codex/2025-07-01-12-36-27 branch July 30, 2025 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants