-
Notifications
You must be signed in to change notification settings - Fork 123
Add Card EncryptedPassword attribute #1181
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
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.
Summary of Changes
Hello @gcatanese, 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 introduces an EncryptedPassword attribute to the CardDetails and CardDonations models. This enhancement allows for the secure handling of one-time passwords or authentication codes provided by cardholders, addressing issue #1180 and expanding the data capabilities of these payment-related objects.
Highlights
- New Attribute: Added EncryptedPassword attribute to CardDetails and CardDonations models.
- Model Enhancements: Updated constructors, properties, and utility methods (ToString, Equals, GetHashCode) in both models to properly integrate the new attribute.
- Documentation Fix: Corrected a documentation link for networkPaymentReference in both model files.
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 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
-
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. ↩
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 adds the EncryptedPassword attribute to the CardDetails and CardDonations models. The changes are consistent across both models, including updates to constructors, ToString, Equals, and GetHashCode methods. I've also noticed a minor fix to a documentation URL.
My main feedback is regarding missing validation for the new EncryptedPassword property in both classes. Other similar encrypted fields have length validation, and adding it for the new property would improve data integrity and consistency. Please see my detailed comments.
| /// <summary> | ||
| /// This field contains an encrypted, one-time password or an authentication code provided by the cardholder. | ||
| /// </summary> | ||
| /// <value>This field contains an encrypted, one-time password or an authentication code provided by the cardholder.</value> | ||
| [DataMember(Name = "encryptedPassword", EmitDefaultValue = false)] | ||
| public string EncryptedPassword { get; set; } |
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.
The new EncryptedPassword property is missing validation. Other encrypted string properties in this class, such as EncryptedCardNumber and EncryptedSecurityCode, have a maximum length validation (15000 characters) within the Validate method. For consistency and to prevent potential issues with oversized data, please consider adding a similar validation for EncryptedPassword.
|
🚢🚢🚢🚢 |
Include
EncryptedPasswordattribute inCardDetailsandCardDonationsFix #1180