You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In general rest routes can be singular or plural: /user or /users. I have seen both in the past.
If using a plural route, it will lead to strange names with feathers-swagger: The single entity is called "users" and multiple entities are called "users list". This is awkward, but only a name of a definition in the swagger file. But it get's you generate code with swagger-codegen or comparable libraries. The names are used as they are and your User type will be a Users.
I think removing some the plural "s" on occurrence would be brittle. Is there a way to configure the name/tag instead of using the path? If not, it would be awesome to have the ability. Or there is perhaps a better solution.
The text was updated successfully, but these errors were encountered:
In general rest routes can be singular or plural:
/user
or/users
. I have seen both in the past.If using a plural route, it will lead to strange names with
feathers-swagger
: The single entity is called "users" and multiple entities are called "users list". This is awkward, but only a name of a definition in the swagger file. But it get's you generate code withswagger-codegen
or comparable libraries. The names are used as they are and yourUser
type will be aUsers
.I think removing some the plural "s" on occurrence would be brittle. Is there a way to configure the name/tag instead of using the path? If not, it would be awesome to have the ability. Or there is perhaps a better solution.
The text was updated successfully, but these errors were encountered: