You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not immediately clear that: the input to this is swagger.json. That's very generic! Many people write their Swagger specs first, and build the code from the spec. Also plenty of people are using other languages with annotations etc. that will allow them to dump a swagger.json from their code. For these people, they might get some use from this library if they know the input is nice and generic like this. If they see PHP immediately, and they aren't using PHP, they may be turned away.
I know the tool is written in PHP, anyway, but the person's web server doesn't need to be written in PHP, and I think that's important.
2c!
The text was updated successfully, but these errors were encountered:
floer32
changed the title
Remove or clarify PHP-specific language from the README?
Remove or clarify (some) PHP-specific language from the README?
Feb 26, 2016
Cool, thanks for sharing this project. Already useful to me. I am not good with PHP so I'm not sure I can submit changes back myself. I may port this to Python/Jinja2 though, so I can make changes rather than just opening issues :P
@saikrishnaradarapu You'll probably want to file a separate ticket for that, with details. But heads up, the project is unmaintained, see #1. You'll probably need to work it out yourself.
It is not immediately clear that: the input to this is
swagger.json
. That's very generic! Many people write their Swagger specs first, and build the code from the spec. Also plenty of people are using other languages with annotations etc. that will allow them to dump aswagger.json
from their code. For these people, they might get some use from this library if they know the input is nice and generic like this. If they see PHP immediately, and they aren't using PHP, they may be turned away.I know the tool is written in PHP, anyway, but the person's web server doesn't need to be written in PHP, and I think that's important.
2c!
The text was updated successfully, but these errors were encountered: