Parameter order in Swagger document doesn't correspond to API

I’m submitting a…

[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Controller method:

Swagger result:

=> configurationName and module is reversed 😕 This has the consequence that e.g. NSwag generated methods also have the wrong parameter order.

Expected behavior

The Swagger doc respects the source-code order.

Bug cause

The problem is that the route parameters decorator metadata (ROUTE_ARGS_METADATA) contains a object, not an array (as DECORATORS.API_PARAMETERS does). => exploreApiReflectedParametersMetadata doesn’t return the correct order.

See the following debugger screenshot.

Sorting parameters by the object keys (i.e. 5:0, 5:1 in the shown example) explicitly, using …

const sortedParameters = lodash_1.map(lodash_1.sortBy(lodash_1.map(parameters, (item, name) => ({item, name})), 'name'), x => x.item);

… fixes the issue (see also debugger screenshot).

[adrianpietka]

The same problem exists for @ApiImplicitParam decorator. Swagger documentation was generated with inverted order for parameters.

My Node.js version: 8.11.3

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.