-
Notifications
You must be signed in to change notification settings - Fork 7
Fix documentation issues #187
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
Conversation
* Fixed code fence with extra backtick * Corrected response class name to Minfraud::HTTPService::Response * Added missing InvalidInputError to exceptions list * Updated copyright year to 2026 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Added guidance to send last four digits for last_digits field * Fixed YARD link syntax for instance attribute references * Fixed SafeKey capitalization Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Fixed event time constraint from 10 years to 1 year * Fixed max value from 1e14 to 1e13 for order amount and cart item price * Fixed shopping cart documentation URLs Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Fixed documentation URLs * Fixed price max value from 1e14 to 1e13 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Changed Fixnum to Integer (Fixnum deprecated in Ruby 2.4+) * Added Minfraud::Model::Error to body return types Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Clarified has_redirect description * Updated status value descriptions for accuracy Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Fixed grammar in distance_to_billing_address description * Added missing @return tag for is_high_risk Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Added: BILLING_REGION_NOT_FOUND, EMAIL_ADDRESS_UNUSABLE, IP_ADDRESS_INVALID, IP_ADDRESS_RESERVED, SHIPPING_REGION_NOT_FOUND Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Summary of ChangesHello @horgh, 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 primarily focuses on a comprehensive review and enhancement of the project's documentation. The changes aim to improve the accuracy, clarity, and completeness of inline comments, README content, and license information. By correcting outdated details, refining descriptions, and adding missing information, this PR ensures that developers have access to precise and up-to-date guidance when working with the codebase. Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this 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 focuses on improving the documentation across the project. The changes include updating copyright years, fixing typos and formatting in README.md and code comments, correcting and clarifying documentation for various components and models to match the API behavior and constraints, adding missing YARD documentation tags, and expanding the list of documented warning codes. All the changes are appropriate and improve the quality and accuracy of the documentation. I have no further suggestions.
No description provided.