[event-channel-managarr]: add Pattern 0b/0c for space-separated YYYY MM DD datetime format#116
Closed
gitdeathbot wants to merge 2 commits into
Closed
[event-channel-managarr]: add Pattern 0b/0c for space-separated YYYY MM DD datetime format#116gitdeathbot wants to merge 2 commits into
gitdeathbot wants to merge 2 commits into
Conversation
…format Peacock Events channels use a space-separated datetime format in their names (e.g. "2026 05 17 11:45:00 AM" or "(2026 06 09 20:00:00)") that none of the existing date patterns in _extract_date_from_channel_name matched. This caused the [PastDate:0] hide rule to be blind to these channels, leaving stale past-dated event channels visible in the guide indefinitely (until the slower [UndatedAge:2] rule eventually caught them after 2 days). Add two new patterns: - Pattern 0b: space-separated datetime in parentheses e.g. Channel Name (2026 06 09 20:00:00) or (2026 06 09 08:00:00 AM) - Pattern 0c: space-separated datetime inline (no parentheses) e.g. Peacock Events 048: Event Name | 2026 04 29 06:01 AM EDT Uses first match so the event date is preferred over any trailing timestamp.
Plugin Validation ResultsModified plugins: 1 PR Closed: UnauthorizedYour GitHub username ( If you are submitting a new plugin, add your GitHub username to the |
dispatcharr-plugins-bot
Bot
added
Plugin Update
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
About this submission
Fix for ECM's
_extract_date_from_channel_namefunction missing Peacock Events-style space-separated datetime formats.What type of change is this?
Description
Peacock Events channels (and similar providers) embed event datetimes in their channel names using a space-separated format:
None of the existing 7 date patterns in
_extract_date_from_channel_namematched this format. As a result, the[PastDate:0]hide rule was blind to these channels — they stayed visible in the guide indefinitely rather than being hidden when their event date passed.Two new patterns added after Pattern 0a:
(YYYY MM DD HH:MM:SS[ AM/PM])YYYY MM DD HH:MM:SS[ AM/PM]re.searchso the first match wins (event date earlier in name preferred over trailing timestamp)Both patterns support optional AM/PM via the existing
_apply_meridiemhelper.Testing
Verified against 6 real Peacock Events channel names — all 6 correctly extracted dates (3 past → hide, 3 future → keep).