Move /locking
and /campaign
routes under /community
#1560
Merged
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.
Summary
The Locking Service was previously only locking-related. As such, we located all routes of the Service under
/locking
. As we are now serving/campaigns
, it does not make sense to have them located under/locking
.This moves all Locking Service-related routes under
/community
, aligning with the domain of the Activity Program.Note: the aforementioned deprecations redirect requests to their relative new route. They will be removed once the client has migrated
Changes
Locking-
module, controller, service toCommunity-
.GET
/v1/locking/campaigns
->/v1/community/campaigns
GET
/v1/locking/campaigns/:campaignId
->/v1/community/campaigns/:campaignId
GET
/v1/locking/campaigns/:campaignId/leaderboard
->/v1/community/campaigns/:campaignId/leaderboard
GET
/v1/locking/leaderboard
->/v1/community/locking/leaderboard
GET
/v1/locking/leaderboard/rank/:safeAddress
->/v1/community/locking/:safeAddress/rank
GET
/v1/locking/:safeAddress/history
->/v1/community/locking/:safeAddress/history