-
-
Notifications
You must be signed in to change notification settings - Fork 231
feat(legacy): add current date macro to string block criteria #3013
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
Merged
Conversation
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
jooola
reviewed
Jun 7, 2024
…criteria-filter # Conflicts: # legacy/application/models/Block.php
Great! Thanks for the contribution! |
jooola
pushed a commit
that referenced
this pull request
Jun 22, 2024
🤖 I have created a release *beep* *boop* --- ## [4.2.0](4.1.0...4.2.0) (2024-06-22) ### Features * **legacy:** add current date macro to string block criteria ([#3013](#3013)) ([451652b](451652b)) * **legacy:** add filename block criteria ([#3015](#3015)) ([4642b6c](4642b6c)) ### Bug Fixes * pin pip version to <24.1 to allow installing pytz (celery) ([#3043](#3043)) ([646bc81](646bc81)) * playlist allocates inaccurate time to smartblocks ([#3026](#3026)) ([2b43e51](2b43e51)) ### Performance Improvements * optimize the api image health check ([#3038](#3038)) ([d99d6e1](d99d6e1)) * optimize the rabbitmq health check ([#3037](#3037)) ([9684214](9684214)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
It is useful to be able to automatically filter tracks to a certain date or day when scheduling tracks for playback. This adds the ability to do just that in any string filter with the
date{format}
macro.This is a new feature
I have updated the documentation to reflect these changes:
Testing Notes
What I did:
I TDD'd the
resolveDate
function in a standalone php playground. I then spun up a local docker stack for libretime and uploaded a few tracks with different dates in one of the metadata tags. I verified that the date macro behaves as expected and filters to tracks using todays date.How you can replicate my testing:
Upload some tracks with date in one of the metadata tags and play around with any string filter.
Links
Closes: #3012