Closed gmathieu closed 8 years ago
Actually, I disagree with this fix, if you use a resource's path that ends in slash, as per defined in the spec, the resourcePathName should be null, right?
I know it does not make sense, but that is the side effect of using slashes at the end or a resource.
Is there another way to define endpoints trailing slashes and still be able to use the resourcePathName
?
There is no variable for the parent
of a resource.
Would you happen to know if 1.0
addresses this?
I found a way to do this. Sorry for the trouble.
# this returned null
/resource/:
get:
...
/{id}:
get:
...
# this works and seems cleaner
/resource:
/:
get:
...
/{id}:
get:
...
Any objections to this PR?