-
Notifications
You must be signed in to change notification settings - Fork 0
feat: fix null error #409
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
base: review
Are you sure you want to change the base?
feat: fix null error #409
Conversation
Summary of ChangesHello @tfhddd, 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 enhances the robustness of the email notification system by addressing a potential null pointer issue. It specifically adds a safeguard in the 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
The pull request aims to fix a nil pointer dereference when sending a notification email. The change adds a nil check for the corporation admin's name. My review points out that there are other similar potential nil pointer issues in the same function for the admin's email address and the link's email address. I've suggested adding checks for these as well to make the function more robust and prevent future panics.
| if corp.Admin.Name == nil { | ||
| return fmt.Errorf("failed to send email msg: admin name is null: %s", link.Id) | ||
| } |
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.
While adding the nil check for corp.Admin.Name is a good fix, this function has other potential nil pointer dereferences that should also be handled. Specifically, corp.Admin.EmailAddr (used on line 171) and link.Email.Addr (used on line 170) could also be nil, leading to panics. It's best to add guard clauses for all of them at the beginning of the function for robustness. I've also updated the error messages to include the corporation ID for better context where applicable.
| if corp.Admin.Name == nil { | |
| return fmt.Errorf("failed to send email msg: admin name is null: %s", link.Id) | |
| } | |
| if corp.Admin.Name == nil { | |
| return fmt.Errorf("failed to send email msg: admin name is null for corp %s", corp.Id) | |
| } | |
| if corp.Admin.EmailAddr == nil { | |
| return fmt.Errorf("failed to send email msg: admin email is null for corp %s", corp.Id) | |
| } | |
| if link.Email.Addr == nil { | |
| return fmt.Errorf("failed to send email msg: link email address is null for link %s", link.Id) | |
| } |
No description provided.