API: Make subscription API more RESTfuL
What does this MR do?
Only use POST requests to subscribe and unsubscribe.
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Merge request reports
Activity
marked the task Documentation created/updated as completed
changed milestone to %9.0
added 292 commits
-
b24cdeef...12cd4c83 - 290 commits from branch
master - 6aeabf32 - API: Make subscription API more RESTfuL
- 68da652d - Update documentation
-
b24cdeef...12cd4c83 - 290 commits from branch
added 2 commits
added 2 commits
assigned to @smcgivern
added 17 commits
-
b6d25d82...c89449e6 - 15 commits from branch
master - 188cea50 - API: Make subscription API more RESTfuL
- 992fbe4e - Update documentation
-
b6d25d82...c89449e6 - 15 commits from branch
-
@razer6 thanks! The code looks good to me, one comment about the docs.
@smcgivern Thanks for the review. I updated the docs.
enabled an automatic merge when the pipeline for 7e6da2ba succeeds
assigned to @razer6
assigned to @smcgivern
added 2 commits
@smcgivern Finally, the specs are passing locally :)
Please register or sign in to reply