Compares the URL of this operation to another.
Compares the URL of this operation to another.
Comparison is based on method and path segments.
For example, GET /pets/{id}
is the same as GET /{type}/{id}
because {type}
is a variable
and can contain pets
.
However, the following are different:
GET /pets
is different to GET /users
because the static paths are differentDELETE /pets/{id}
is different to PUT /pets/{id}
because methods are different
True
if the URI templates are ambiguous and 2 or more unique end points can resolve to
either URI templates. False
otherwise..
Full path from combining the rootPath
with relativePath
.
The full path split into path segments for ease of matching
The full path split into path segments for ease of matching
If path = /user/{Id}
and rootUrl in the config is /api
, the full path segment are
List( PathSegment("api", false), PathSegment("user", false), PathSegment("Id", true) )
Compares the URL template with the specified end point.
Compares the URL template with the specified end point.
For example, GET /pets/{id}
matches the end point GET /pets/123
.
End point to match
True
if this is a match; False
if not a match.
HTTP method.
HTTP method. e.g. GET
.
Path relative to the rootPath
for the REST operation
The relative URL template split into path segments for ease of matching
The relative URL template split into path segments for ease of matching
If path = /user/{Id}
and rootUrl in the config is /api
, the relative path segment are
List( PathSegment("user", false), PathSegment("Id", true) )
Root path of the REST service.
Root path of the REST service. e.g. /api
.
Number of static path segments.
Number of static path segments. Used to determine best match
The HTTP method and path to a REST operation
HTTP method. e.g.
GET
.Root path of the REST service. e.g.
/api
.Path relative to the
rootPath
for the REST operation