Skip to content

missing / when concatenating sub-resources creates invalid swagger api-docs #721

Closed
@todd-richmond

Description

@todd-richmond

found in 1.3.10

leading / are not required in Jersey annotations so you can have

@Path("foo")
class Foo {
@GET 
public Response getFoo() {
}

@GET @Path("bar")
public Response getBar() {
}

which correctly handles the resource path /foo/bar

However, swagger forgets to include / in concatenations so this converts to 2 api sets - /foo and /foobar instead of /foo/bar. The only workaround I see is to use @get @path("/bar") which does create /foo/bar

Also note that swagger does properly prefix /foo in both basePath, resourcePath and apis/path values so this seems to only be a problem with sub-resources

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions