Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Error responses #39

Open
leon-mrks opened this issue Jun 13, 2023 · 4 comments
Open

Error responses #39

leon-mrks opened this issue Jun 13, 2023 · 4 comments

Comments

@leon-mrks
Copy link

The docs don't show any stated error responses. No matter if the 200 status code is supplied or not (or any positive response).

(#35)

Example:

/*
 * Title 
 *
 * @response {
 *   "status": 200
 * }
 *
 * @response 400 {
 *   "status": 400
 * }
 * @response 404 {
 *   "status": 404
 * }
 * 
 * / 

Outputs:
CleanShot 2023-06-13 at 17 02 34

@jubag-93
Copy link

I have the same problem on my project, I wait for a resolution. Thanks!

apriliaan added a commit to apriliaan/idoc that referenced this issue Jul 17, 2023
@ovac
Copy link
Owner

ovac commented Jul 27, 2023

@apriliaan Thank you for the excellent fix.

ovac added a commit that referenced this issue Jul 27, 2023
@kristianstarkloffjedox
Copy link

I have still the same problem. But I downloaded the project with composer and in composer.json I see the version 1.6. So, if there would be new version, people would also get this change included when using composer.

@ovac
Copy link
Owner

ovac commented Oct 22, 2023

I am not sure what you mean. Can you please elaborate?
@jubag-93, do you still have the same problem after the new version release?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants