-
Notifications
You must be signed in to change notification settings - Fork 33
Open
Description
The feature that allows a user to specify a "tag" key in route configuration to override the tag generated automatically from the controller identity is no longer working when no controller and action defined.
In upgrading from 2.9 to 3.3.0 we found need to change the key from "tag" to "tags". When a controller and action defined then the generated documentation groups the endpoint under the specified "tags" key. When no controller and action defined the behavior is that it ignores the "tags" key and groups under the controller identity name.
Metadata
Metadata
Assignees
Labels
No labels