Support QUERYPARAM Variable Substitution #5265
Merged
Conversation
This file contains 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
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.
This PR will...
Implement EXT-X-DEFINE QUERYPARAM support
Why is this Pull Request needed?
The EXT-X-DEFINE QUERYPARAM attribute is a new HLS feature that allows the definition of HLS variables based on URL search parameter key value pairs. A URL param from the playlist's parent URL can used as a variable to substitute variable declarations (
{$var-name}) inside URI strings and quoted string attributes anywhere in an HLS playlist following the variable definition, just like variables defined by the EXT-X-DEFINE NAME/VALUE or IMPORT attribute(s) (#5161).Resolves issues:
Resolves #5240
Checklist