We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For fields that need to be set in the API, e.g. the Month field in URIMonth and QueryMonth, thebinding:"required" tag should be set.
Month
URIMonth
QueryMonth
binding:"required"
Errors on binding should be handled with e.g. a middleware, see gin-gonic/gin#430 (comment) for inspiration.
With this, the parseMonthQuery could probably be removed, too.
parseMonthQuery
There should be only one struct for API responses with the fields data, error and links ideally, so that all responses can be handled in the same way.
data
error
links
The text was updated successfully, but these errors were encountered:
Current state pushed to chore/error-handling
chore/error-handling
Sorry, something went wrong.
No branches or pull requests
For fields that need to be set in the API, e.g. the
Month
field inURIMonth
andQueryMonth
, thebinding:"required"
tag should be set.Errors on binding should be handled with e.g. a middleware, see gin-gonic/gin#430 (comment) for inspiration.
With this, the
parseMonthQuery
could probably be removed, too.There should be only one struct for API responses with the fields
data
,error
andlinks
ideally, so that all responses can be handled in the same way.The text was updated successfully, but these errors were encountered: