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 pull request, a grand symphony of schema refinement and component orchestration, introduces sweeping changes to the very fabric of episode and show data, both within the hallowed halls of the API and the bustling cityscapes of the client. Prepare to witness a transformation of structure and elegance.
API Schema Updates:
episodeIdsResponseSchema
, a meticulous catalog of episode identities, emerges from the depths of the API, defining the structure of these essential identifiers.episodeResponseSchema
, a tome of detailed episode knowledge, unfolds, revealing optional incantations for extended requests and deeper insights.showIdsResponseSchema
, an extension of the episode ID lexicon, adds a touch ofslug
magic, enhancing the identification of shows.showResponseSchema
, a grand repository of show data, materializes, offering optional image fields for those seeking a visual feast.showListResponseSchema
undergoes a metamorphosis, embracing the newly forgedepisodeResponseSchema
andshowResponseSchema
in place of its previous inline definitions.upNextResponseSchema
, a harbinger of anticipation, emerges, weaving together the threads of episode and show schemas to reveal the tapestry of future viewing.sync
router, a gateway to data synchronization, expands its dominion to include the "up next" endpoint, guarded by the newly crafted response schema.Client-Side Updates:
package.json
scroll, a record of dependencies, welcomes thetemporal-polyfill
incantation, ensuring the smooth passage of time across all realms.EpisodeCover.svelte
component, a canvas for episode presentation, undergoes a stylistic and structural refinement, enhancing the display of episode tags.EpisodeTagContent.svelte
component, a humble vessel of tag information, sheds its former name and emerges as the more versatileTagContent.svelte
, its influence spreading across the diverse landscape of tag components.ShowProgressTag.svelte
component, a beacon of progress, materializes, illuminating the user's journey through the vast expanse of a show's narrative.UpNextEpisode.svelte
component, a herald of anticipation, takes center stage, utilizing the new schemas and components to showcase the episodes that await.upNext.ts
script, a conduit to the API's depths, emerges, tasked with retrieving and transforming "up next" data for the client's consumption.Configuration Update:
.vscode/settings.json
grimoire, a repository of development configurations, receives an incantation for automated import organization, ensuring a tidy and harmonious codebase.This grand orchestration of changes enhances the structure and consistency of API responses, while simultaneously enriching the client-side experience. The interplay of schemas and components creates a symphony of data and presentation, paving the way for a more refined and engaging Trakt Lite experience.