drop backend client

[JarbasAl]

Summary by CodeRabbit

• Chores
  • Removed the ovos-backend-client dependency from the requirements.
  • Added the spotipy dependency to the requirements.
  • Updated import paths for OAuth-related components in the Spotify integration.
  • Increased version requirement for ovos-utils to >=0.5.0.

[coderabbitai]

Walkthrough

The changes involve updates to the requirements.txt file and modifications in the spotify.py file. In requirements.txt, the dependency on ovos-backend-client has been removed, and spotipy has been added. Additionally, the version constraint for ovos-utils has been increased. In spotify.py, the import statements for OAuthTokenDatabase and OAuthApplicationDatabase have been updated to reflect a new source module, while the existing functionality and error handling remain unchanged.

Changes

File	Change Summary
requirements.txt	- Updated dependency: ovos-utils from >=0.1.0 to >=0.5.0 - Removed dependency: ovos-backend-client - Added dependency: spotipy
spotify.py	- Updated import path for OAuthTokenDatabase and OAuthApplicationDatabase from ovos_backend_client.database to ovos_utils.oauth - Changed method logic in get_access_token to call get_oauth_token

Poem

In the garden of code, changes bloom bright,
Removing old roots, adding new light.
With spotipy now in the mix,
Our Spotify tunes will surely fix!
Hopping along, we embrace the new,
A rabbit's delight in each line we view! 🐇✨

Warning

Rate limit exceeded

@JarbasAl has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 19 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between cb28efc and 960057c.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between cb28efc and 960057c.

📒 Files selected for processing (1)

• requirements.txt (1 hunks)

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

• requirements.txt

---

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 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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7a052b1 and f78dbf5.

📒 Files selected for processing (2)

• requirements.txt (1 hunks)
• spotify.py (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• spotify.py

🔇 Additional comments (1)

requirements.txt (1)

1-3: LGTM! Backend client removal aligns with PR objectives.

The removal of ovos-backend-client while maintaining other core OVOS dependencies is consistent with the PR's goal.

[coderabbitai]

⚠️ Potential issue

Add version constraints for spotipy dependency.

The spotipy dependency should have version constraints to ensure:

• Consistent builds across environments
• Protection against breaking changes
• Security through pinned versions

-spotipy
+spotipy>=2.19.0,<3.0.0

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	spotipy
	spotipy>=2.19.0,<3.0.0