-
Notifications
You must be signed in to change notification settings - Fork 60
*: bugfix and refactor prefix semantics #41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*: bugfix and refactor prefix semantics #41
Conversation
lucab
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I didn't know about actix-web .prefix().
I've left a few minor comments, looks fine in general.
ae5e7db to
65f2ccc
Compare
The bugfix and semantic change is that the prefix keeps, and if necessary adds, a leading slash. This simplifies the logic of dealing with prefixes because it doesn't require special-casing for emtpy namespaces which was buggy before. Using actix-web's prefix method removes the need to specify the prefix for every new route.
65f2ccc to
50f28ec
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lucab, steveeJ The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The bugfix and semantic change is that the prefix keeps, and if
necessary adds, a leading slash. This simplifies the logic of dealing
with prefixes because it doesn't require special-casing for emtpy
namespaces which was buggy before.
Using actix-web's prefix method removes the need to specify the prefix
for every new route.
Fixes up #38.