-
Notifications
You must be signed in to change notification settings - Fork 1
Add support to get associated accounts #37
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
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Summary of ChangesHello @pantherale0, 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 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 adds support for retrieving associated accounts by leveraging the business partner number from the access token. The changes are logical and well-contained, introducing a new API method, updating the authentication flow to include the business partner ID in requests, and adjusting the test script accordingly. One area for improvement is a type hint mismatch where None is passed for a parameter typed as dict. Additionally, I've noticed that send_request in pyanglianwater/auth.py creates a new aiohttp.ClientSession for each call, which is inefficient. It would be better to reuse the session stored in self._auth_session to benefit from connection pooling.
This PR adds support to retrieve the associated accounts of a business partner number.
We extract the BP number from the access token and therefore this is one less item a user will need to identify.
An example response:
Related discussion: home-assistant/core#156225 (comment)