You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we currently only return the schedule for the next 60 days from libretime, shows with less frequent episodes don't look nice on the page:
This affects other shows as well, but this analysis is based on a suivre. Initially we settled on 60d of "next" data because there were often errors in the schedule further out.
To support more use cases, we should return the schedule for a much longer time period from libretime. A range that would fix a suivre and then some would be to return the next 6 months (183d).
Doing this would increase the size of the returned JSON considerably. The current result is 156K, the new one would be 428K. Storage wise this isn't much, but it feels like the increase in size might have a notable impact on page loading times.
If my concern is valid, then we might need to explore other options, like splitting the file into monthly chunks.
I'll try to test this, most likely over the upcoming weekend, and either update this issue to reflect my findings or close it if the fix works.
The text was updated successfully, but these errors were encountered:
Since we currently only return the schedule for the next 60 days from libretime, shows with less frequent episodes don't look nice on the page:
This affects other shows as well, but this analysis is based on a suivre. Initially we settled on 60d of "next" data because there were often errors in the schedule further out.
To support more use cases, we should return the schedule for a much longer time period from libretime. A range that would fix a suivre and then some would be to return the next 6 months (183d).
Doing this would increase the size of the returned JSON considerably. The current result is 156K, the new one would be 428K. Storage wise this isn't much, but it feels like the increase in size might have a notable impact on page loading times.
If my concern is valid, then we might need to explore other options, like splitting the file into monthly chunks.
I'll try to test this, most likely over the upcoming weekend, and either update this issue to reflect my findings or close it if the fix works.
The text was updated successfully, but these errors were encountered: