Creates unsubscribe api endpoint and functionality to expect a competition_id and northstar_id and unsubscribe user from competition_user pivot table
How should this be manually tested?
POST to gladiator.dev/api/v1/unsubscribe with a northstar_id, and a competition_id similiar to :
gladiator.dev/api/v1/unsubscribe?northstar_id=5894e9437f43c217dd158b49&competition_id=6
and check local dev to see if that user was unsubscribed (1 value in unsubscribed column in competition_user pivot table)
sbsmith86
commented
7 years ago
What's this PR do?
Creates unsubscribe api endpoint and functionality to expect a competition_id and northstar_id and unsubscribe user from competition_user pivot table
How should this be manually tested?
POST to gladiator.dev/api/v1/unsubscribe with a northstar_id, and a competition_id similiar to : gladiator.dev/api/v1/unsubscribe?northstar_id=5894e9437f43c217dd158b49&competition_id=6 and check local dev to see if that user was unsubscribed (1 value in unsubscribed column in competition_user pivot table)
What are the relevant tickets?
Fixes #379