Parser ignoring responses

Question

Parser ignoring responses

sheinfeld opened this issue 4 years ago · 13 comments

Good afternoon, first of all let me thank you for this amazing package!

I am trying to add the responses to the documentation, but once generated I only get the default 200 and nothing else.

/** * @response 200 { * "status": "success", * "message": "Your request was successfully created" * } * * @response 500 { * "status": "error", * "message": ["Custom error message"] * } */

Do I need to add/change anything?

Answer 1 · 2021-03-30T18:17:47.000Z

I have the same problem, I take material from the documentation, but any responses other than 200 are not displayed

Answer 2 · 2021-03-30T19:06:33.000Z

@RodionovSlsUp I just managed to fix some of it, you'll now be able to render multiple responses: sheinfeld/idoc

My next step will be to render the response data parameters like the body ones: https://i.imgur.com/BGQRj3K.png

Stay tuned

Answer 3 · 2021-03-30T20:04:58.000Z

Also just updated the core JS library to it's latest version, looks way better!

Answer 4 · 2021-03-30T20:11:10.000Z

@sheinfeld in fact, I did about the same thing myself :)

There are very few response fields, it's true

Answer 5 · 2021-03-30T20:14:06.000Z

@sheinfeld
Thomas, tell me, is it possible to use your fork through the composer?
And also, is there an understanding, in terms of time, when it will be possible to make the response fields?

Thank you very much, you are cool

Answer 6 · 2021-03-30T20:17:21.000Z

Hey @RodionovSlsUpx Unfortunately we can’t actually used forked ones, but I’ll make an independent version so we and others can make use of an updated version! I’ll try have it ready by the end of the week!

On Tue, 30 Mar 2021 at 21:14, RodionovSlsUp ***@***.***> wrote: @sheinfeld <https://github.com/sheinfeld> Thomas, tell me, is it possible to use your fork through the composer? And also, is there an understanding, in terms of time, when it will be possible to make the response fields? Thank you very much, you are cool — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIGTXAFSRGKCFCNNOWNTC23TGIWJ5ANCNFSM4S3EXH4Q> .

-- Best regards, Tomas C. Lopes (Sent from my mobile)

Answer 7 · 2021-03-30T20:28:23.000Z

@sheinfeld
Thank you very much, if it's not difficult to call me, mark or write to the mail v.rodionov@sls-up.ru

Answer 8 · 2021-03-30T20:41:42.000Z

@sheinfeld by the way, your 500 error is marked as a success. I have not figured out how to elegantly solve this problem and moved the blanks with an error to the config. And I draw the name according to the code from the config.You can see examples in the screenshot

Answer 9 · 2021-04-01T12:37:25.000Z

@RodionovSlsUp I'm looking at it now :D

Answer 10 · 2021-04-01T12:48:08.000Z

@RodionovSlsUp just commit into my forked rep a solution!

I am working on this now:

Answer 11 · 2021-10-12T13:57:14.000Z

@ovac will this be merged back into your repo? Thanks for the hard work btw.. idoc is appreciated very much over here!

Answer 12 · 2021-10-12T14:01:06.000Z

BTW, this issue is blocking the phpunit tests driven by hotmeteor/spectator.. if that would work its a great combination.
Ofcourse I can check out @sheinfeld 's repo, but I prefer the composer approach , so I'd rather not.

Answer 13 · 2021-10-15T04:26:45.000Z

@ronaldwanink, Thank you very much for your kind comment. I will be merging the feature with the next release. I however will want all tests to run successfully though.