cli: implement --player-external-http-continuous #4739
Merged
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.
Resolves #4738
No tests, because no tests have ever been written for
output_stream_http()
or the entirestreamlink_cli.utils.http_server
module.There are two choices that can be made for implementing the new CLI argument:
--player-external-http-continuous=bool
requiring a boolean value and affecting the logic of the main argument--player-external-http
.The issue with this is that it's not consistent with the logic of the
--player-http
and--player-continuous-http
arguments, which are individual arguments. It's also not consistent with the naming scheme (which I just realized), so it probably has to be changed to--player-external-continuous-http
.--player-external-http
and--player-external-http-non-continuous
, similar to--player-http
and--player-continuous-http
. As you can see, the default logic of--player-external-http
already is "continuous", so the second argument name has to be negated, which is not great.Thoughts?