romalytvynenko

@layerok I would be happy to accept a PR for this issue with some tests 😇

I don't really understand the motivation behind this feature.

@MarnuLombard I was considering to merge, but manual response attributes were coming so I've waited on it. I've just added `#[Response]` attribute (it will be available in the next release)...

Hey @gigerIT This is the issue behind Stoplight Elements UI 🥲 Scramble generates the following schema: ```json { "type": "object", "properties": { "size": { "description": "The list of opened jobs...

@lcyoong Can you please show the pieces of your real code so I can reproduce? Anything that can be reproduced but in the real context

@lcyoong ```php class GroupController extends BaseController { private $status = 200; /** * List of groups */ public function index(GetGroups $getGroups) { return response()->json([ 'foo' => 'bar' ], $this->status); }...

Hey @krzkz94 This is indeed a problem. Related to https://github.com/dedoc/scramble/issues/650. I plan to work on it, but I'm still thinking how to approach this. One way is to document array...

@PaulKiddle The schema you suggest will be expecting an array of strings for `tags[]` parameter. Meaning that for `tags` parameter it will be an array of string arrays (`string[][]`).

@PaulKiddle I think we can stick to your [suggested way with this example](https://swagger.io/specification/#:~:text=An%20optional%20query%20parameter%20of%20a%20string%20value,%20allowing%20multiple%20values%20by%20repeating%20the%20query%20parameter). My only concern about it is how Stoplight Elements UI will render this parameter: ``` { "name":...

@krzkz94 @PaulKiddle The fix is released in `v0.12.24`: https://github.com/dedoc/scramble/releases/tag/v0.12.24 (But please bump to 0.12.25 as it contains performance fixes)