-
Notifications
You must be signed in to change notification settings - Fork 16
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
Revert "fix: remove duplicate imports that will lead to failed js #75
Conversation
…lds" This reverts commit 5756869.
📝 WalkthroughWalkthroughAhem, most esteemed gentlemen and ladies of the technological realm, I present a most refined update to the Plex API specification. The modifications involve the strategic addition of Plex-specific parameters across several operational endpoints, including library searches, pin retrieval, server resources, and user authentication. These parameters shall provide additional contextual metadata about the client's environment, enhancing the API's discriminatory capabilities. Changes
Poem
Quite splendid, if I do say so myself. adjusts monocle 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
@LukeHagar Can you give your blessing? |
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.
Actionable comments posted: 4
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (6)
src/paths/library/get-search-all-libraries.yaml
(1 hunks)src/paths/pins/pins-id.yaml
(1 hunks)src/paths/pins/pins.yaml
(1 hunks)src/paths/resources/get-server-resources.yaml
(1 hunks)src/paths/users/post-sign-in.yaml
(1 hunks)src/pms-spec.yaml
(1 hunks)
🧰 Additional context used
🪛 GitHub Check: Trunk Check
src/paths/resources/get-server-resources.yaml
[failure] 27-27: yamllint(quoted-strings)
[new] string value is redundantly quoted with any quotes
src/paths/library/get-search-all-libraries.yaml
[failure] 10-10: yamllint(quoted-strings)
[new] string value is redundantly quoted with any quotes
🪛 yamllint (1.35.1)
src/pms-spec.yaml
[warning] 58-58: missing starting space in comment
(comments)
🔇 Additional comments (4)
src/paths/pins/pins.yaml (1)
21-25
: Most splendid additions, if I do say so myself!
I must say, dear colleague, the inclusion of these Plex-specific parameters is most appropriate and follows the established patterns across the API specification. The parameters shall provide most valuable context about the client's environment.
src/paths/resources/get-server-resources.yaml (1)
27-27
: A most proper addition, indeed!
The inclusion of the Plex identifier parameter maintains consistency with our other distinguished endpoints, most notably the pins and authentication services.
🧰 Tools
🪛 GitHub Check: Trunk Check
[failure] 27-27: yamllint(quoted-strings)
[new] string value is redundantly quoted with any quotes
src/paths/users/post-sign-in.yaml (1)
11-15
: Most splendid addition of client context parameters, good sir!
I must say, the restoration of these Plex-specific parameters is most appropriate for the authentication endpoint. These parameters provide essential context about the client making the request, which is paramount for proper authentication handling.
src/pms-spec.yaml (1)
56-64
: 🧹 Nitpick (assertive)
A temporary measure requiring future attention, if I may say so.
Most astute of you to document the SDK generation predicament with a TODO comment. However, might I suggest creating a tracking issue to ensure this temporary solution doesn't become permanent? This would help ensure the matter receives proper attention once the SDK generation conundrum is resolved.
Let me verify if a tracking issue exists:
🧰 Tools
🪛 yamllint (1.35.1)
[warning] 58-58: missing starting space in comment
(comments)
@@ -24,6 +24,7 @@ | |||
description: Include IPv6 entries in the results | |||
schema: | |||
$ref: "../../models/common/PlexBoolean.yaml" | |||
- $ref: "../../parameters/plex/x-plex-identifier.yaml" |
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.
🧹 Nitpick (assertive)
A minor matter of quotation, if you'll permit me to observe.
One might consider removing the redundant quotes around the reference path, as they serve no additional purpose in this context.
- - $ref: "../../parameters/plex/x-plex-identifier.yaml"
+ - $ref: ../../parameters/plex/x-plex-identifier.yaml
📝 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.
- $ref: "../../parameters/plex/x-plex-identifier.yaml" | |
- $ref: ../../parameters/plex/x-plex-identifier.yaml |
🧰 Tools
🪛 GitHub Check: Trunk Check
[failure] 27-27: yamllint(quoted-strings)
[new] string value is redundantly quoted with any quotes
- $ref: ../../parameters/plex/x-plex-identifier.yaml | ||
- $ref: ../../parameters/plex/x-plex-product.yaml | ||
- $ref: ../../parameters/plex/x-plex-device.yaml | ||
- $ref: ../../parameters/plex/x-plex-version.yaml | ||
- $ref: ../../parameters/plex/x-plex-platform.yaml |
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.
🧹 Nitpick (assertive)
A most excellent enhancement to our authentication protocol!
I am pleased to report that these additional parameters shall provide a more robust security context for our authentication flow. The consistency with our other endpoints is most commendable.
Might I suggest documenting these parameters' role in enhancing security in the API documentation? It would be most beneficial for our esteemed API consumers.
@@ -7,6 +7,7 @@ | |||
Search the provided query across all library sections, or a single section, and return matches as hubs, split up by type. | |||
parameters: | |||
- $ref: "../../parameters/query.yaml" | |||
- $ref: "../../parameters/plex/x-plex-identifier.yaml" |
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.
🧹 Nitpick (assertive)
A most proper addition of the identifier parameter, though a minor refinement is warranted.
The inclusion of the Plex identifier parameter is most appropriate. However, I must point out that the quotation marks around the reference path are quite redundant, my good fellow.
Might I suggest this refined presentation:
- - $ref: "../../parameters/plex/x-plex-identifier.yaml"
+ - $ref: ../../parameters/plex/x-plex-identifier.yaml
📝 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.
- $ref: "../../parameters/plex/x-plex-identifier.yaml" | |
- $ref: ../../parameters/plex/x-plex-identifier.yaml |
🧰 Tools
🪛 GitHub Check: Trunk Check
[failure] 10-10: yamllint(quoted-strings)
[new] string value is redundantly quoted with any quotes
- $ref: "./parameters/plex/x-plex-device.yaml" | ||
# TODO: Enable this when the SDK generation bug has been resolved: | ||
# https://github.com/LukeHagar/plexjs/issues/26#issuecomment-2547058955 | ||
#x-speakeasy-globals: |
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.
🧹 Nitpick (assertive)
A minor matter of proper comment formatting, if you'll permit me to mention.
The comment on line 58 appears to be missing a space after the hash symbol, which is customary in YAML documents.
Might I suggest this slight refinement:
-#x-speakeasy-globals:
+# x-speakeasy-globals:
📝 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.
#x-speakeasy-globals: | |
# x-speakeasy-globals: |
🧰 Tools
🪛 yamllint (1.35.1)
[warning] 58-58: missing starting space in comment
(comments)
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.
This looks good for now
This reverts commit 5756869.
Summary by CodeRabbit
New Features
Bug Fixes
Documentation