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
// @Summary // @Description // @Tags // @Accept json // @Produce json // @Param X-Tenant-Type header string true "1: admin, 2: merchant, 3: app" default(1) // @Param X-Uuid header string true "user uuid" default(2463649890798928897) // @Param X-TemporaryToken header string true "user uuid" default(OJVERWCLUOXRHZXRZGEHYK2UWLUSS3X4) // @Param params body api.VerifyOtpRequest true "params" // @Header 200 {string} X-Uuid "312312312" // @Header 200 {string} Token "qwerty" // @Success 200 {object} api.HTTPResponse "errCode: Err_OTP_Vefify(100000)" // @Failure 400 {object} api.HTTPError // @Router /v1/api/otpsecret-bind [post]
why response header not generated?
responses: "200": description: OK schema: $ref: '#/definitions/api.HTTPResponse' "400": description: Bad Request schema: $ref: '#/definitions/api.HTTPError'
The text was updated successfully, but these errors were encountered:
Headers must be below the responses
Sorry, something went wrong.
I never used this feature but don't you think is quite weird to have this kind of restriction?
No branches or pull requests
why response header not generated?
The text was updated successfully, but these errors were encountered: