minor fixes and remove x-speakeasy-retries

[JasonLandbridge]

Summary by CodeRabbit

• New Features
  • Enhanced API functionality with a new endpoint for managing the watchlist.
  • Added a new optional parameter type for fetching specific media types in the library items.
• Improvements
  • Updated API documentation for better clarity on parameters and response structures.
  • Introduced retry logic for API requests to improve reliability.
• Changes
  • Modified required fields and property types for user account definitions to allow for more flexibility.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The recent modifications encompass substantial updates to the OpenAPI specifications across several files. Notably, the UserPlexAccount.yaml file has seen alterations in property definitions, including changes to required fields and type flexibility. The get-library-items.yaml file has been enhanced with expanded descriptions and new parameters for improved API clarity. Lastly, the pms-spec.yaml file now reflects an updated version, the introduction of a watchlist endpoint, and a retry strategy, thereby augmenting the API's overall functionality.

Changes

File	Change Summary
src/models/UserPlexAccount.yaml	- Removed examples section. - Updated required fields: added attributionPartner, removed pin. - Modified types for several fields to allow null values. - Updated services array to allow null types for token, secret, and subscriptionDescription. - Updated description for roles field.
src/paths/library/[sectionKey]/get-library-items.yaml	- Expanded description for tag parameter. - Added new optional parameter type. - Clarified includeGuids parameter. - Updated MediaContainer response schema with detailed structure.
src/pms-spec.yaml	- Version updated from 0.0.2 to 0.0.3. - New endpoint /library/sections/watchlist/{filter} added. - Expanded x-speakeasy-globals with new references. - Introduced x-speakeasy-retries section detailing retry strategy.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant API
    participant Database

    Client->>API: Request get-library-items
    API->>Database: Fetch library items based on parameters
    Database-->>API: Return library items
    API-->>Client: Respond with MediaContainer

Loading

"In the realm of code, a dance did unfold,
With types and fields, a story retold.
From watchlists anew to retries in play,
The API blossoms, brightening the way.
A toast to the changes, both grand and small,
In the world of Plex, we shall have a ball! 🎩✨"

---

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.