Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat / up-next (read-only mode) #23

Merged
merged 8 commits into from
Nov 14, 2024
Merged

feat / up-next (read-only mode) #23

merged 8 commits into from
Nov 14, 2024

Conversation

vladjerca
Copy link
Collaborator

@vladjerca vladjerca commented Nov 13, 2024

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:

  • The episodeIdsResponseSchema, a meticulous catalog of episode identities, emerges from the depths of the API, defining the structure of these essential identifiers.
  • The episodeResponseSchema, a tome of detailed episode knowledge, unfolds, revealing optional incantations for extended requests and deeper insights.
  • The showIdsResponseSchema, an extension of the episode ID lexicon, adds a touch of slug magic, enhancing the identification of shows.
  • The showResponseSchema, a grand repository of show data, materializes, offering optional image fields for those seeking a visual feast.
  • The venerable showListResponseSchema undergoes a metamorphosis, embracing the newly forged episodeResponseSchema and showResponseSchema in place of its previous inline definitions.
  • The upNextResponseSchema, a harbinger of anticipation, emerges, weaving together the threads of episode and show schemas to reveal the tapestry of future viewing.
  • The 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:

  • New i18n messages, whispered in both English and French, herald the arrival of the "up next" feature, ensuring a multilingual welcome.
  • The package.json scroll, a record of dependencies, welcomes the temporal-polyfill incantation, ensuring the smooth passage of time across all realms.
  • The EpisodeCover.svelte component, a canvas for episode presentation, undergoes a stylistic and structural refinement, enhancing the display of episode tags.
  • The EpisodeTagContent.svelte component, a humble vessel of tag information, sheds its former name and emerges as the more versatile TagContent.svelte, its influence spreading across the diverse landscape of tag components.
  • The ShowProgressTag.svelte component, a beacon of progress, materializes, illuminating the user's journey through the vast expanse of a show's narrative.
  • The UpNextEpisode.svelte component, a herald of anticipation, takes center stage, utilizing the new schemas and components to showcase the episodes that await.
  • The 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:

  • The .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.

@seferturan seferturan merged commit e264417 into main Nov 14, 2024
3 checks passed
@seferturan seferturan deleted the feat/up_next branch November 14, 2024 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants