[RE-000] Add chargebacks to charge

[ezerozen]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello, 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 API's data model by introducing comprehensive support for chargebacks. It defines new data structures for representing chargeback-related files and the chargeback itself, and seamlessly integrates this information directly into the charge object. This provides a more complete and accessible view of charge-related events, improving the clarity and functionality of the API for handling chargeback scenarios.

Highlights

• New Schema for Chargeback Files: Introduced a new API schema, chargeback_file_response, to represent individual files associated with a chargeback, such as evidence documents.
• New Schema for Chargeback Details: Defined a new API schema, chargeback_response, which encapsulates all relevant details of a chargeback, including its status, reason, and associated files.
• Integration with Charge Response: Integrated the newly defined chargeback_response schema into the existing charge_response schema, allowing charge objects to directly include comprehensive chargeback information when applicable.

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

Changelog

• _build/api.yaml
  • Added chargeback_file_response schema definition.
  • Added chargeback_response schema definition.
  • Included chargeback field referencing chargeback_response in charge_response.
• schemas/chargebacks/chargeback_file_response.yml
  • Created new file defining the chargeback_file_response object.
• schemas/chargebacks/chargeback_response.yml
  • Created new file defining the chargeback_response object.
• schemas/charges/charge_response.yml
  • Added chargeback field referencing ../chargebacks/chargeback_response.yml.

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 chargeback-related schemas and integrates them into the charge response. The changes are well-structured. My review includes suggestions to improve the API contract by using enums for status and reason fields, ensuring consistency in defining nullable fields according to the OpenAPI 3.1 standard, and refining schema descriptions for better clarity.