Release 1.13.1

[jschlyter]

Summary by CodeRabbit

• Version Update

  • Updated Polestar API component version from 1.13.0 to 1.13.1

• Code Improvement

  • Enhanced token retrieval process to ensure a new token is fetched regardless of current validity.
  • Refined control flow in the token retrieval method for improved clarity.

[coderabbitai]

Walkthrough

This pull request involves updating the version number for the Polestar API component in the manifest file from "1.13.0" to "1.13.1" and refining the token retrieval method in the authentication module. The get_token method in the PolestarAuth class has been modified to include a return statement after the token refresh operation, clarifying the control flow. Additionally, the get_ev_data method in the PolestarApi class has been updated to call get_token() with a force=True argument to ensure a new token is fetched.

Changes

File	Change Summary
custom_components/polestar_api/manifest.json	Version updated from "1.13.0" to "1.13.1"
custom_components/polestar_api/pypolestar/auth.py	Modified get_token method to add return statement after token refresh
custom_components/polestar_api/pypolestar/polestar.py	Updated get_ev_data method to call get_token() with force=True

Possibly related PRs

• Rework token acquire/refresh logic #282: Changes in the get_token method of the PolestarAuth class related to token management logic.
• Release 1.13.0 #284: Version update in the manifest.json file from "1.12.0" to "1.13.0" is directly related to the version update from "1.13.0" to "1.13.1".

Suggested reviewers

• BJReplay

Poem

🐰 A Rabbit's Ode to Token Refresh 🔑

Version bumped with gentle care,
Token logic now more fair,
A return statement, crisp and bright,
Guiding auth with rabbit might!

Hop, hop, code refines its way! 🚀

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

custom_components/polestar_api/pypolestar/polestar.py (1)

200-200: Consider potential rate-limiting and performance overhead from forced token refresh.

While forcing a token refresh ensures a valid token for subsequent calls, continuously calling get_token(force=True) might result in unnecessary requests if this method is called too frequently. If possible, confirm that you will not exceed your API’s rate limits and avoid redundant token fetching in rapid succession.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a847642 and 5038a9b.

📒 Files selected for processing (3)

• custom_components/polestar_api/manifest.json (1 hunks)
• custom_components/polestar_api/pypolestar/auth.py (1 hunks)
• custom_components/polestar_api/pypolestar/polestar.py (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• custom_components/polestar_api/manifest.json
• custom_components/polestar_api/pypolestar/auth.py