feat(ofrep): add header, base URI, and timeout options

[erka]

This PR

• add WithHeader(), WithBaseURI(), and WithTimeout() configuration options.
• improve error handling to include underlying error causes.
• set Content-Type header to application/json in HTTP requests.
• fix typo in test error message and update dependencies.

Related Issues

• [BUG] errors.Is cannot detect original cause go-sdk#437

[gemini-code-assist]

Summary of Changes

Hello @erka, I'm Gemini Code Assist¹! 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 significantly enhances the OFREP provider by adding crucial configuration options for HTTP headers, base URI, and request timeouts. It also refines error handling to provide more detailed insights into failures and standardizes the Content-Type header for all outgoing HTTP requests. These changes aim to improve the provider's usability, robustness, and adherence to best practices.

Highlights

• New Configuration Options: Introduced WithHeader(), WithBaseURI(), and WithTimeout() options for more flexible OFREP provider configuration.
• Enhanced Error Handling: Improved error reporting by passing underlying error causes to of.ResolutionError constructors, providing richer context for debugging.
• HTTP Content-Type Enforcement: Ensured all HTTP requests made by the OFREP provider explicitly set the Content-Type header to application/json.
• Dependency Updates and Minor Fixes: Updated Go module dependencies and corrected a minor typo in a test error message.

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

[gemini-code-assist]

Code Review

This pull request introduces several valuable enhancements to the OFREP provider, including new configuration options for headers, base URI, and timeouts. The error handling is also improved by wrapping underlying errors, which will greatly aid in debugging. Additionally, it correctly sets the Content-Type header for requests and fixes a minor typo.

My review includes a suggestion to add validation for the baseUri at provider creation to prevent runtime errors, which would improve the robustness of the provider. I've also pointed out a few places where the error wrapping can be simplified to avoid redundant information in error messages. Overall, these are solid improvements.

[erka]

what @gemini-code-assist suggests is right, but it’ll cause breaking changes for someone.