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
Fetches all challenges which are not deleted and released. Deleted challenges will have deleted set to true, and released challenges will have a date in released_at. Only users with ViewUpcomingWeeklyChallenge permission should be able to see unreleased challenges.
If the user can see deleted challenges, deleted should be added in the challenge response
Endpoints
GET @ /challenges
Fetches all challenges which are not deleted and released. Deleted challenges will have
deleted
set to true, and released challenges will have a date inreleased_at
. Only users withViewUpcomingWeeklyChallenge
permission should be able to see unreleased challenges.Challenge Object should look something like this:
if the user has any
WeeklyChallenges
permission, they should be able to see deleted challenges.POST @ /challenges
Creates a new Challenge. If the challenge is created successfully should return
201 Created
with the challenge data.Body
GET @ /challenges/{id/slug}
Fetch said challenge by id or slug.
Challenge object should something similar to this:
PATCH @ /challenges/{id}
Updates said challenge. Should return
200 OK
with the new challenge data.Body
PUT @ /challenges/{id}/release
Releases/Unreleases said challenge. Should return
204 No Content
if executed successfully.DELETE @ /challenges/{id}
Update said challenge and set
deleted
to true. If executed successfully204 No Content
should be returned.The text was updated successfully, but these errors were encountered: