RouteScope.readAuth property causes an unexpected behaviour in Swagger.

If I set up `routeOptions.readAuth: false` inside a model, Swagger stops requiring authorisation header for many other routes. Not only in GET, but in POST and PUT as well..

Is there anyone else having this problem??

No file or test is named. Reproduce the behavior with a model using routeOptions.readAuth: false, then trace how RouteScope.readAuth affects Swagger authorization across GET, POST, and PUT routes; done when disabling authorization for one route no longer changes other routes.

Written by the indexing model from the issue text.