Currently I believe the behavior is that the get on currentVideos is returning a 'Recommendation[]' that consists of 3 fields, videoId, topicId, clipIndex.
Unfortunately fetching the user through the GET/user will not resolve the videoId to a VideoMetadataDocument, and require the frontend to use the GET video fetch afterwards. We should instead provide an endpoint that will just get and resolve both the videometadata and the clipmetadata
GET user currentVideos
Team
Backend
Description:
Currently I believe the behavior is that the get on currentVideos is returning a 'Recommendation[]' that consists of 3 fields, videoId, topicId, clipIndex.
Unfortunately fetching the user through the GET/user will not resolve the videoId to a VideoMetadataDocument, and require the frontend to use the GET video fetch afterwards. We should instead provide an endpoint that will just get and resolve both the videometadata and the clipmetadata