Open stringerbell opened 8 years ago
Currently, only optional params are exposed when looking at a service.
Example:
It'd be awesome to add support for non-optional params
In Service.php, in the toArray() method, this is happening:
Service.php
toArray()
$routeWithReplacements = str_replace(['[', ']', '{/', '{:'], ['{', '}', '/{', '{'], $service->route);
Changing it to:
$routeWithReplacements = preg_replace('#\[?\/:(\w+)\]?#', '/{$1}', $service->route);
will give the results I'd like to see.
If this change is acceptable, I can go ahead and make a PR, otherwise, I'm open to hearing other ideas to add support for this.
This repository has been closed and moved to laminas-api-tools/api-tools-documentation-swagger; a new issue has been opened at https://github.com/laminas-api-tools/api-tools-documentation-swagger/issues/10.
Currently, only optional params are exposed when looking at a service.
Example:
It'd be awesome to add support for non-optional params
Example:
In
Service.php
, in thetoArray()
method, this is happening:$routeWithReplacements = str_replace(['[', ']', '{/', '{:'], ['{', '}', '/{', '{'], $service->route);
Changing it to:
$routeWithReplacements = preg_replace('#\[?\/:(\w+)\]?#', '/{$1}', $service->route);
will give the results I'd like to see.
If this change is acceptable, I can go ahead and make a PR, otherwise, I'm open to hearing other ideas to add support for this.