New continuous parameter, Plex will automatically play the next episode in the series #36077
Conversation
home-assistant
bot
added
has-parent
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
📝 WalkthroughWalkthroughThe changes introduce a new Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant PlexIntegration
participant PlexServer
User->>PlexIntegration: Request to play media with continuous=true
PlexIntegration->>PlexServer: Send play_media command with continuous parameter
PlexServer-->>PlexIntegration: Acknowledge command
PlexIntegration-->>User: Media playback started
PlexServer->>PlexServer: Automatically play next episode
Warning Rate limit exceeded@siemon-geeroms has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 42 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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. 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 (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (5)
source/_posts/2024-12-01-the-month-of-what-the-heck.markdown (2)
126-126: Remove trailing spaceThere's a trailing space at the end of line 126.
-[ability to organize automations] and the ability to +[ability to organize automations] and the ability to🧰 Tools
🪛 Markdownlint (0.35.0)
126-126: Expected: 0 or 2; Actual: 1
Trailing spaces(MD009, no-trailing-spaces)
163-205: Use consistent emphasis styleThe FAQ section uses underscores for emphasis while the rest of the document uses asterisks. For consistency, use asterisks throughout.
Example fix for the first FAQ question:
-**_"Great! I have multiple things! Should I put all my stuff in a single - topic?!"_** +**_"Great! I have multiple things! Should I put all my stuff in a single + topic?!"**_🧰 Tools
🪛 LanguageTool
[style] ~164-~164: Using many exclamation marks might seem excessive (in this case: 25 exclamation marks for a text that’s 7267 characters long)
Context: ... I put all my stuff in a single topic?!”_** No, please create **multiple...(EN_EXCESSIVE_EXCLAMATION)
[uncategorized] ~176-~176: Possible missing preposition found.
Context: ...appen. The goal is to lower the barrier reporting things for one month. Code contributo...(AI_HYDRA_LEO_MISSING_OF)
[style] ~179-~179: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ... to address. However, we have picked up a lot of items over the years (including bigge...(A_LOT_OF)
[style] ~192-~192: Use ‘will’ instead of ‘going to’ if the following action is certain.
Context: ...pic is one of the top-voted ones, so it is going to be fixed/addressed, right?”_** Thi...(GOING_TO_WILL)
[style] ~197-~197: The phrase ‘lots of’ might be wordy and overused. Consider using an alternative.
Context: ...or too big to implement. A topic with lots of votes is more likely to be noticed by a...(A_LOT_OF)
🪛 Markdownlint (0.35.0)
163-163: Expected: asterisk; Actual: underscore
Emphasis style(MD049, emphasis-style)
164-164: Expected: asterisk; Actual: underscore
Emphasis style(MD049, emphasis-style)
173-173: Expected: asterisk; Actual: underscore
Emphasis style(MD049, emphasis-style)
173-173: Expected: asterisk; Actual: underscore
Emphasis style(MD049, emphasis-style)
184-184: Expected: asterisk; Actual: underscore
Emphasis style(MD049, emphasis-style)
185-185: Expected: asterisk; Actual: underscore
Emphasis style(MD049, emphasis-style)
192-192: Expected: asterisk; Actual: underscore
Emphasis style(MD049, emphasis-style)
193-193: Expected: asterisk; Actual: underscore
Emphasis style(MD049, emphasis-style)
204-204: Expected: asterisk; Actual: underscore
Emphasis style(MD049, emphasis-style)
205-205: Expected: asterisk; Actual: underscore
Emphasis style(MD049, emphasis-style)
source/_integrations/plex.markdown (1)
164-164: Fix parameter documentation formattingThe parameter documentation has a formatting inconsistency with the dash. Let's align it with the style of other parameters in the list.
-- `continuous`: Plex will automatically play the next episode in the series. Accepts `1` or `true` to enable. +- `continuous`: Plex will automatically play the next episode in the series. Accepts `1` or `true` to enable.🧰 Tools
🪛 LanguageTool
[uncategorized] ~164-~164: Loose punctuation mark.
Context: ...edia for a specific user. -continuous: Plex will automatically play the next e...(UNLIKELY_OPENING_PUNCTUATION)
source/_integrations/myuplink.markdown (2)
63-66: Consider adding rate limit handling information.While the polling interval is clearly specified, it would be helpful to add information about what happens if rate limits are exceeded and how the integration handles such situations.
## Data updates The integration will poll the API for data every 60 seconds. This polling interval is designed to work within the rate limits of myUplink APIs while providing timely updates. + +If rate limits are exceeded, the integration will [describe behavior, e.g., "automatically back off and retry after a delay" or "log a warning message"].
72-76: Consider expanding troubleshooting scenarios.While the login issue is well documented, consider adding more common troubleshooting scenarios such as:
- Connection timeout issues
- Entity mapping problems
- Rate limit exceeded situations
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (1)
source/images/blog/2024-12-01-the-month-of-what-the-heck/social.jpgis excluded by!**/*.jpg
📒 Files selected for processing (3)
source/_integrations/myuplink.markdown(2 hunks)source/_integrations/plex.markdown(1 hunks)source/_posts/2024-12-01-the-month-of-what-the-heck.markdown(1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_posts/2024-12-01-the-month-of-what-the-heck.markdown
[uncategorized] ~29-~29: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ..., as of this year, we are also [the #1 open source project on GitHub]! A lot has happened...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[formatting] ~53-~53: These punctuation marks differ from each other. Use only one if you are ending a sentence.
Context: ...### Lowering the barrier for sharing WTH?! moments We realize reporting bugs on o...
(DOUBLE_PUNCTUATION_PREMIUM)
[style] ~67-~67: The phrase ‘talk about’ can be informal. To elevate your writing, consider using a more professional alternative.
Context: ...gory] as a safe, lower-barrier place to talk about your Home Assistant “What the heck?!” m...
(TALK_ABOUT_DISCUSS)
[style] ~82-~82: The phrase ‘pretty much’ can be informal. To strengthen your writing, consider removing it or replacing it with an adverb.
Context: ...ld it be? The answers to this question pretty much capture the goal behind this month: Fin...
(PRETTY_MUCH)
[typographical] ~100-~100: A comma is not needed after quotations ending in either question marks or exclamation points.
Context: ...opics for the month of “What the heck?!”, I hope they inspire you for more topics...
(COMMA_AFTER_QUESTION_QUOTE)
[uncategorized] ~146-~146: Possible missing comma found.
Context: ...sharing your WTH! 👆That title says it all really. Start sharing your “What th...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~164-~164: Using many exclamation marks might seem excessive (in this case: 25 exclamation marks for a text that’s 7267 characters long)
Context: ... I put all my stuff in a single topic?!”_** No, please create **multiple...
(EN_EXCESSIVE_EXCLAMATION)
[uncategorized] ~176-~176: Possible missing preposition found.
Context: ...appen. The goal is to lower the barrier reporting things for one month. Code contributo...
(AI_HYDRA_LEO_MISSING_OF)
[style] ~179-~179: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ... to address. However, we have picked up a lot of items over the years (including bigge...
(A_LOT_OF)
[style] ~192-~192: Use ‘will’ instead of ‘going to’ if the following action is certain.
Context: ...pic is one of the top-voted ones, so it is going to be fixed/addressed, right?”_** Thi...
(GOING_TO_WILL)
[style] ~197-~197: The phrase ‘lots of’ might be wordy and overused. Consider using an alternative.
Context: ...or too big to implement. A topic with lots of votes is more likely to be noticed by a...
(A_LOT_OF)
[style] ~207-~207: ‘by all means’ might be wordy. Consider a shorter alternative.
Context: ...u are comfortable using GitHub, please, by all means, [file an issue report on GitHub] ins...
(EN_WORDINESS_PREMIUM_BY_ALL_MEANS)
source/_integrations/plex.markdown
[uncategorized] ~164-~164: Loose punctuation mark.
Context: ...edia for a specific user. - continuous: Plex will automatically play the next e...
(UNLIKELY_OPENING_PUNCTUATION)
🪛 Markdownlint (0.35.0)
source/_posts/2024-12-01-the-month-of-what-the-heck.markdown
126-126: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
144-144: Punctuation: '!'
Trailing punctuation in heading
(MD026, no-trailing-punctuation)
12-12: null
Images should have alternate text (alt text)
(MD045, no-alt-text)
163-163: Expected: asterisk; Actual: underscore
Emphasis style
(MD049, emphasis-style)
164-164: Expected: asterisk; Actual: underscore
Emphasis style
(MD049, emphasis-style)
173-173: Expected: asterisk; Actual: underscore
Emphasis style
(MD049, emphasis-style)
173-173: Expected: asterisk; Actual: underscore
Emphasis style
(MD049, emphasis-style)
184-184: Expected: asterisk; Actual: underscore
Emphasis style
(MD049, emphasis-style)
185-185: Expected: asterisk; Actual: underscore
Emphasis style
(MD049, emphasis-style)
192-192: Expected: asterisk; Actual: underscore
Emphasis style
(MD049, emphasis-style)
193-193: Expected: asterisk; Actual: underscore
Emphasis style
(MD049, emphasis-style)
204-204: Expected: asterisk; Actual: underscore
Emphasis style
(MD049, emphasis-style)
205-205: Expected: asterisk; Actual: underscore
Emphasis style
(MD049, emphasis-style)
🔇 Additional comments (7)
source/_posts/2024-12-01-the-month-of-what-the-heck.markdown (1)
1-10: Verify date consistency and image accessibility
- The post date in the front matter (November 30) doesn't match the filename date (December 1)
- The OG image should be verified for existence and accessibility
✅ Verification successful
Date mismatch is intentional for scheduled posts
The date difference between the filename (December 1) and front matter (November 30) is a common pattern for scheduled blog posts, where the filename indicates the intended publication date while the front matter contains the creation date. The OG image exists and is accessible at the specified path.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if the OG image exists and is accessible
if [ -f "source/images/blog/2024-12-01-the-month-of-what-the-heck/social.jpg" ]; then
echo "OG image exists"
else
echo "OG image is missing"
fi
Length of output: 121
source/_integrations/plex.markdown (2)
Line range hint 171-173: LGTM! Clear and helpful token configuration note
The note effectively communicates the token requirement and provides a practical workaround for users who need the IP allowlist feature.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~161-~161: Loose punctuation mark.
Context: ...rwise plays at the beginning. - offset: The desired playback start position in ...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~162-~162: Loose punctuation mark.
Context: ... position in seconds. - allow_multiple: A search must find one specific item to...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~163-~163: Loose punctuation mark.
Context: ...ts 1 or true to enable. - username: A username for a local Plex user accoun...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~163-~163: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ed if the Plex server has multiple users and you wish to play media for a specific u...
(COMMA_COMPOUND_SENTENCE)
[uncategorized] ~164-~164: Loose punctuation mark.
Context: ...edia for a specific user. - continuous: Plex will automatically play the next e...
(UNLIKELY_OPENING_PUNCTUATION)
164-164: Verify documentation completeness
Let's ensure the documentation covers all aspects of the new continuous playback feature.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~164-~164: Loose punctuation mark.
Context: ...edia for a specific user. - continuous: Plex will automatically play the next e...
(UNLIKELY_OPENING_PUNCTUATION)
source/_integrations/myuplink.markdown (4)
29-35: LGTM! Clear and informative introduction.
The description effectively communicates the integration's purpose and includes an important note about subscription requirements.
67-71: LGTM! Well-documented limitations.
The section clearly explains the limitations and provides proper guidance for users encountering mapping issues.
78-82: LGTM! Clear removal instructions.
The removal instructions are complete and include the important step of cleaning up credentials from the myUplink developer site.
42-44: Verify the application registration fields.
The field names and callback URL look correct, but let's verify they match the current myUplink developer portal interface.
| og_image: /images/blog/2024-12-01-the-month-of-what-the-heck/social.jpg | ||
| --- | ||
|
|
||
| <a href='https://community.home-assistant.io/c/month-of-what-the-heck/61'><img src='/images/blog/2024-12-01-the-month-of-what-the-heck/social.jpg' style='border: 0;box-shadow: none;'></a> |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add alt text to the banner image
The banner image is missing alternative text, which is important for accessibility.
-<a href='https://community.home-assistant.io/c/month-of-what-the-heck/61'><img src='/images/blog/2024-12-01-the-month-of-what-the-heck/social.jpg' style='border: 0;box-shadow: none;'></a>
+<a href='https://community.home-assistant.io/c/month-of-what-the-heck/61'><img src='/images/blog/2024-12-01-the-month-of-what-the-heck/social.jpg' style='border: 0;box-shadow: none;' alt='Month of What the Heck 2024 banner'></a>📝 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.
| <a href='https://community.home-assistant.io/c/month-of-what-the-heck/61'><img src='/images/blog/2024-12-01-the-month-of-what-the-heck/social.jpg' style='border: 0;box-shadow: none;'></a> | |
| <a href='https://community.home-assistant.io/c/month-of-what-the-heck/61'><img src='/images/blog/2024-12-01-the-month-of-what-the-heck/social.jpg' style='border: 0;box-shadow: none;' alt='Month of What the Heck 2024 banner'></a> |
🧰 Tools
🪛 Markdownlint (0.35.0)
12-12: null
Images should have alternate text (alt text)
(MD045, no-alt-text)
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
siemon-geeroms
force-pushed
the
patch-2
branch
from
eb4ba00
to
f9994c6
Compare
siemon-geeroms
changed the title
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
source/_integrations/plex.markdown (1)
164-164: Add example usage and fix punctuation
- Remove the leading hyphen and align with other parameter formatting
- Consider adding an example in the TV episode section showing continuous playback
- - `continuous`: Plex will automatically play the next episode in the series. Accepts `1` or `true` to enable. + `continuous`: Plex will automatically play the next episode in the series. Accepts `1` or `true` to enable.Consider adding this example under the TV episode examples section:
# Play Rick and Morty episodes continuously starting from S2E5 entity_id: media_player.plex_player media_content_type: EPISODE media_content_id: '{ "library_name": "Adult TV", "show_name": "Rick and Morty", "season_number": 2, "episode_number": 5, "continuous": 1 }'🧰 Tools
🪛 LanguageTool
[uncategorized] ~164-~164: Loose punctuation mark.
Context: ...edia for a specific user. -continuous: Plex will automatically play the next e...(UNLIKELY_OPENING_PUNCTUATION)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
source/_integrations/plex.markdown(1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/plex.markdown
[uncategorized] ~164-~164: Loose punctuation mark.
Context: ...edia for a specific user. - continuous: Plex will automatically play the next e...
(UNLIKELY_OPENING_PUNCTUATION)
🔇 Additional comments (1)
source/_integrations/plex.markdown (1)
164-164: LGTM! Documentation clearly explains the new continuous parameter
The documentation for the new continuous parameter is clear, concise, and follows the existing documentation style. It properly explains the functionality and accepted values.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~164-~164: Loose punctuation mark.
Context: ...edia for a specific user. - continuous: Plex will automatically play the next e...
(UNLIKELY_OPENING_PUNCTUATION)
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (2)
source/_integrations/plex.markdown (2)
164-164: LGTM! Minor formatting suggestion.The documentation for the new
continuousparameter is clear and consistent with other parameters. However, there's a minor formatting issue with the bullet point.-- `continuous`: Plex will automatically play the next episode in the series. Accepts `1` or `true` to enable. +- `continuous`: Plex will automatically play the next episode in the series. Accepts `1` or `true` to enable.🧰 Tools
🪛 LanguageTool
[uncategorized] ~164-~164: Loose punctuation mark.
Context: ...edia for a specific user. -continuous: Plex will automatically play the next e...(UNLIKELY_OPENING_PUNCTUATION)
225-229: Fix table formatting.The table content is correct, but there are trailing spaces in the markdown table that should be removed for consistency.
-| Data attribute | Description | -| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Data attribute | Description | +| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |🧰 Tools
🪛 Markdownlint (0.35.0)
226-226: Expected: 0 or 2; Actual: 30
Trailing spaces(MD009, no-trailing-spaces)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
source/_integrations/plex.markdown(4 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/plex.markdown
[uncategorized] ~164-~164: Loose punctuation mark.
Context: ...edia for a specific user. - continuous: Plex will automatically play the next e...
(UNLIKELY_OPENING_PUNCTUATION)
🪛 Markdownlint (0.35.0)
source/_integrations/plex.markdown
226-226: Expected: 0 or 2; Actual: 30
Trailing spaces
(MD009, no-trailing-spaces)
263-263: null
Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
🔇 Additional comments (1)
source/_integrations/plex.markdown (1)
Line range hint 164-263: Documentation changes align with PR objectives.
The documentation changes effectively cover the new continuous parameter feature:
- Clear parameter description
- Updated table structure
- Practical example
🧰 Tools
🪛 Markdownlint (0.35.0)
226-226: Expected: 0 or 2; Actual: 30
Trailing spaces
(MD009, no-trailing-spaces)
231-231: Punctuation: ':'
Trailing punctuation in heading
(MD026, no-trailing-punctuation)
source/_integrations/plex.markdown
Outdated
| Play Rick and Morty episodes continuously starting from S2E5 | ||
|
|
||
| ```yaml | ||
| entity_id: media_player.plex_player | ||
| media_content_type: EPISODE | ||
| { "library_name": "Adult TV", "show_name": "Rick and Morty", "season_number": 2, "episode_number": 5, "continuous": 1}' | ||
| ``` |
There was a problem hiding this comment.
Fix JSON formatting in the example.
The example is helpful but contains formatting issues:
- Missing opening quote in the JSON string
- Missing blank lines around the code block
Play Rick and Morty episodes continuously starting from S2E5
```yaml
entity_id: media_player.plex_player
media_content_type: EPISODE
-{ "library_name": "Adult TV", "show_name": "Rick and Morty", "season_number": 2, "episode_number": 5, "continuous": 1}'
+media_content_id: '{ "library_name": "Adult TV", "show_name": "Rick and Morty", "season_number": 2, "episode_number": 5, "continuous": 1 }'
<details>
<summary>🧰 Tools</summary>
<details>
<summary>🪛 Markdownlint (0.35.0)</summary>
263-263: null
Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
</details>
</details>
<!-- This is an auto-generated comment by CodeRabbit -->
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (3)
source/_integrations/plex.markdown (3)
164-164: Add period for consistency with other parameter descriptions.The description of the
continuousparameter should end with a period to maintain consistency with other parameter descriptions.- - `continuous`: Plex will automatically play the next episode in the series. Accepts `1` or `true` to enable. + - `continuous`: Plex will automatically play the next episode in the series. Accepts `1` or `true` to enable.🧰 Tools
🪛 LanguageTool
[uncategorized] ~164-~164: Loose punctuation mark.
Context: ...edia for a specific user. -continuous: Plex will automatically play the next e...(UNLIKELY_OPENING_PUNCTUATION)
257-263: Fix formatting issues in the example.
- Add blank lines around the code block
- Format the JSON for better readability
Play Rick and Morty episodes continuously starting from S2E5 + ```yaml entity_id: media_player.plex_player media_content_type: EPISODE -media_content_id: '{ "library_name": "Adult TV", "show_name": "Rick and Morty", "season_number": 2, "episode_number": 5, "continuous": 1}' +media_content_id: '{ + "library_name": "Adult TV", + "show_name": "Rick and Morty", + "season_number": 2, + "episode_number": 5, + "continuous": 1 +}'
<details> <summary>🧰 Tools</summary> <details> <summary>🪛 Markdownlint (0.35.0)</summary> 263-263: null Fenced code blocks should be surrounded by blank lines (MD031, blanks-around-fences) </details> </details> --- `164-164`: **Consider adding a note about interaction with maxresults.** Since the PR objectives mention that "Plex now defaults to playing a single episode of a series when the parameter `maxresults` is set to 1", it would be helpful to document how the `continuous` parameter interacts with or overrides this behavior. <details> <summary>🧰 Tools</summary> <details> <summary>🪛 LanguageTool</summary> [uncategorized] ~164-~164: Loose punctuation mark. Context: ...edia for a specific user. - `continuous`: Plex will automatically play the next e... (UNLIKELY_OPENING_PUNCTUATION) </details> </details> </blockquote></details> </blockquote></details> <details> <summary>📜 Review details</summary> **Configuration used: CodeRabbit UI** **Review profile: CHILL** <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between 71fa270233a0ee9ef8b0530e396faffaaa88c2a8 and 7b0c4f35dcedb29be7ba230a133a9b9552b77eac. </details> <details> <summary>📒 Files selected for processing (1)</summary> * `source/_integrations/plex.markdown` (3 hunks) </details> <details> <summary>🧰 Additional context used</summary> <details> <summary>🪛 LanguageTool</summary> <details> <summary>source/_integrations/plex.markdown</summary> [uncategorized] ~164-~164: Loose punctuation mark. Context: ...edia for a specific user. - `continuous`: Plex will automatically play the next e... (UNLIKELY_OPENING_PUNCTUATION) </details> </details> <details> <summary>🪛 Markdownlint (0.35.0)</summary> <details> <summary>source/_integrations/plex.markdown</summary> 263-263: null Fenced code blocks should be surrounded by blank lines (MD031, blanks-around-fences) </details> </details> </details> <details> <summary>🔇 Additional comments (1)</summary> <details> <summary>source/_integrations/plex.markdown (1)</summary> `225-229`: **LGTM! Parameter documentation is clear and well-structured.** The `continuous` parameter is properly documented in the TV episode parameters table with consistent formatting. </details> </details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
Proposed change
Plex now defaults to playing a single episode of a series when maxresults = 1. However, with the new continuous parameter, Plex will automatically play the next episode in the series.
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.Summary by CodeRabbit
New Features
continuousparameter for the Plex integration, enabling automatic playback of the next episode in a series.Documentation
continuousparameter and clarified the use of optional keys in themedia_content_idJSON payload.continuousparameter for TV episodes.