OperantionId may be duplicated

Now a days operationId is generated based on the endpoint method name. So when you have two methods with the same name (even in different classes) it causes a conflict in the swagger.json file.

For example:

@ApiOperation(value = "Just testing")
@Path("test-one")
public class Test {
    @GET
    @Path("test")
    public Response test() {
        return Response.ok().build();
    }
}

@ApiOperation(value = "Testing...")
@Path("test-two")
public class Test2 {
    @GET
    @Path("another-test")
    public Response test() {
        return Response.ok().build();
    }
}

The operationId property in the final file will be test for both endpoints.

[ChristianLutz]

@larsf

I solved this problem with a filterClass

public class OperationIdPrefixFilter extends AbstractSpecFilter {

	@Override
	public Optional<Operation> filterOperation(Operation operation, ApiDescription api, Map<String,
			List<String>> params, Map<String, String> cookies, Map<String, List<String>> headers) {
		String operationId = operation.getOperationId();
		operation.setOperationId(operationId.split("_[0-9]+$")[0]);

		return super.filterOperation(operation, api, params, cookies, headers);
	}
}

[larsf]

This change cause swagger-codegen to generate methods that now have “arbitrary” numbers in the name. So in stead of being able to call “endpoint”.delete(), depending on how many endpoints you have, it may be endpoint.delete_1(), or endpoint.delete_100(). When you allowed for the operationId to simply be equal to the method name, the api calls were consistent like this: firstEndpoint.delete() and secondEndpoint.delete(), instead of now being firstEndpoint.delete_1(), and secondEndpoint.delete_2()

Is there a way to override this auto numbering, and revert to the old behavior?