feature(Schedule V2): App & Widget v2 Handling #61
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.
I've added handling for the v2 schedule from the API, this should now match the web where we can grab the day names from the API instead of the names being hardcoded on the front-end. It should also mean we have the flexibility to have as many days (though the UI wouldn't fit more than 4 😉) as we want now.
I've verified that this functionality works on old schedules which had the singular day, and this years schedule.
Also put an update in for the widget which was hardcoded to 2022 but can't run on a device due to AppStoreConnect permission limitations and the simulator wasn't playing ball for the widget to show correctly so pretty much put it in blindly if someone can check that 😆
Changes
scheduleDateDecodingStrategybecause the v2 API sends down date formats in different formats (that was a fun one) for Day/Slots & Event so applying a singular .iso8601 formatter to the whole decode didn't work as expectedScreenshots