Still, laravel, being so popular has no such implementation and i think this needs to be a priority for the team.
There are plenty of community libraries like dedoc but they have a long way from full support or need alot of docblocks to make sense.
The laravel team has the opportunity to implement such a feature by integrating it with its classes, in the same way the router can give you a list of ruotes, their methods and the controller 'executing' the action.
I tried on my own to test the waters and i dont think i would be able to do much better than dedoc scramble is doing due to limitations, my thinking in the way mapping works.
Plenty of teams use api docs, heck even having an internal documentation is amazing, not to speak about public apis.
What do you think about this? I would go ahead and start doing it myself but my skillet is not up there, and even then i dont see myself doing anything other than static analysis, which kinda results in the current available setups
Edit: if i wasnt clear, the idea is that for public libraries to have a full-baked setup they have to first get the routes(using the route class), use reflection to get info about the request that validates the data + its validation methods, then using static analysis to detect responses (correct me if wrong, but this was my impression after trying it myself). As far as we appressiate what the community is doing, having laravel at least give a hand into it is more than welcome, not to mention an official setup submitted by /u/EmptyBrilliant6725
[link] [comments]
0 comments:
Post a Comment
Thanks