APIs are not always fully public and you might want to generate a doc for public users and another documentation for internal use. This feature needs a bit of discussion on how to implement it, though.
Maybe the most flexible would be some twig helpers so that you can make your own doc template and dump the docs for the routes you want. Then you can create as many templates as you want.
I am facing a similar problem. Is it possible to hide specific routes inside the documentation if you have multiple routes inside a doc-tag? If not, @Seldaek can you elaborate a little bit more about the approach with the twig-helpers (or point me in the right direction)?
@benbender I thought instead of relying on the bundle default api doc route, you could build your own controller/template that renders explicitly some routes by name, or maybe a given "section" of the docs so you could use that as a tag. That wouldn't really help if you have two routes on one controller though.
I've found another solution which is, I think, a better and more flexible approach. See my according pr #155. For now I have to subclass the ApiDocExtractor and change the class-parameter to do this. With the pr, this would be nativly possible. I also thought of a kind of filter-api for the routes but do not want to fiddle with the existing api too deep for now...
So I need to create a private documentation or a documentation that would be available via a different endpoint than our public documentation. What is the recommended way to do that today?
I'm trying to understand how you did it (you = @benbender ) but I don't understand...
@marcw This should be solved with the merge of #155