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
{{ message }}
This repository has been archived by the owner on May 23, 2024. It is now read-only.
Right now, @api-throws has support for a dictionary-like type and subtype system where you can do {User} as your throws description to generate a description of "If the User cannot be found.".
It might be worth investigating at looking to replace that with a configurable dictionary of these types of common return, error, and parameter descriptions that you could easily drop in.
For example:
@api-throws:private {403} \ErrorRepresentationIf the user was not found.
Imagine setting up a dictionary in your config like:
<dictionaries>
<descriptionid="user.not_found">If the user was not found.</description>
</dictionaries>
Right now,
@api-throws
has support for a dictionary-like type and subtype system where you can do{User}
as your throws description to generate a description of "If the User cannot be found.".It might be worth investigating at looking to replace that with a configurable dictionary of these types of common return, error, and parameter descriptions that you could easily drop in.
For example:
Imagine setting up a dictionary in your config like:
And then doing:
We should also retain the current sprintf-like functionality and support something like:
Just an idea to consolidate and have consistent documentation error messaging.
The text was updated successfully, but these errors were encountered: