fix: new episode notifications for subscriptions not opening series page when clicking #1554
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.
There are multiple scenarios where the previous approach fails at the moment:
dataUrl,handleIntentDatatries to match the JSON data to the main url of the engine, which obviously won't work because the JSON data isn't prefixed with themainUrlmainUrlis different to the useddataUrlfor the series (e.g. because the mainUrl is the HTML url for the extension, but the internally used urls refer to the api url for the extension), there's no matchTMDBinternally to reference series (i.e. their TMDB URL). However, such providers either don't provide anymainUrl, and if they do, it's not guaranteed that the user will land on the right extension when clicking the link, because multiple providers possible use the samemainUrl.The idea in this PR is to use the api name in order to identify the origin of the notifications
dataUrl, so that the right api can be found (by its name).