Unable to use `swagger_context` in subresource

[jeffreymb]

I have a subresource definition on a DTO class as follows:

 *     subresourceOperations={
 *          "chapters_get_subresource"={
 *              "path"="bibles/{version}/books/{book}/chapters",
 *              "swagger_context"={
 *                  "parameters"={
 *                      {"name"="version", "in"="path", "type"="string", "required"=true},
 *                      {"name"="book", "in"="path", "type"="string", "required"=true},
 *                  },
 *              },
 *          },
 *     },

The swagger_context has no effect in the swagger UI. Am I doing something wrong or is this a bug?

[soyuka]

example: https://github.com/gries/api-platform/pull/1/files#diff-03658d5f5162523638fa095aac8fb995R21

This is not a subresource but should be a custom collection operation IMHO.

[jeffreymb]

Perhaps you are correct that this should be a custom collection operation instead of a subresource, but the bug remains that it isn't currently possible to set a custom swagger context in a subresource.

[soyuka]

Indeed swagger_context is missing here. Although I'm not sure that we should support this because you shouldn't need it and do a custom operation instead :).

[soyuka]

merging with #2706

[brunonic]

In my case, I need to change my subresource operation tags in swagger, it's not possible now and this is not cool.