feat(up-next): switch to nitro endpoint #412
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.
Up Next Performance Boost: Introducing the Nitro Endpoint
This pull request introduces a new, optimized "nitro" version of the "up next" endpoint and updates the client to utilize this enhanced functionality.
API Changes
standard
andnitro
endpoints to theupNext
router in the API. This provides two versions of the "up next" endpoint: the standard version and the optimized "nitro" version.Client Changes
upNextRequest
function to use thestandard
endpoint and exported themapUpNextResponse
function for reusability.upNextQueryNitro.ts
, for thenitro
endpoint, including the request function and query definition.UpNextList.svelte
component to dynamically determine the type of endpoint to use based on a URL parameter, ensuring the appropriate query is used for fetching data.useUpNextEpisodes
store to accept atype
parameter and use the corresponding query for either thestandard
ornitro
endpoint, providing flexibility in data fetching.(This change, like a skilled mechanic souping up a classic car, introduces a "nitro" version of the "up next" endpoint, significantly boosting performance and efficiency. The updated client components seamlessly integrate with the new endpoint, providing users with a faster and more responsive experience when accessing their upcoming media.)
Test: http://localhost:5173/?up-next=nitro