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.
While integrating the the latest stremio-video into stremio-web, in order to start sending videoParams to subtitles addons, i found an issue with how stremio-core and stremio-web worked together.
The only way to integrate all parts together is by detaching the videoParams from the player's selected prop. (or a massive refactor down to the useCoreModel hook and potentially every route of stremio-web)
This change is a breaking change for stremio-android-tv. It needs to send this new PlayerAction::VideoParamsUpdated instead of new Load action once video params are ready. @TheBeastLT Does that look like a simple change or it will cause massive refactor on your side?
The functionality can be tested in stremio-web gh pages on this url: https://stremio.github.io/stremio-web/update-stremio-video/#/player/eJwVysENgDAIAMBdGKB8fHUbrAQbSyAFjYlxd+O974FzDqiwZ3pUxEibJFzETAaT9yjNFOWi1W5U3jphkPrg+G87ivoC7wel8Bou/https%3A%2F%2Fv3-cinemeta.strem.io%2Fmanifest.json/https%3A%2F%2Fv3-cinemeta.strem.io%2Fmanifest.json/movie/tt420/tt420
which load some stock video with an arbitrary tt prefixed id
In the network tab you can see the opensubtitles request with the correct params.
...
The PR is based on this commit because there are some changes in development branch which are not compatible with core-web's deveopment branch.
CI fails for some unrelated reason