Added support for private APIs#530
Added support for private APIs#530justinnichols wants to merge 1 commit intoapidoc:masterfrom justinnichols:private_api_support
Conversation
Added @apiPrivate to support the ability to specify if an API is a private API. apidoc now also has a --private false|true parameter on the command line that defaults to false. If false, it does not include any API block that contains @apiPrivate. If true, it will include the API (assuming the API is also not marked as @apiIgnore).
|
Corresponding: apidoc/apidoc-core#46 |
|
Thank you, merged in the next version. |
|
@rottmann I'm a little confused. Are you just copy/pasting the code changes? Or is the next version different enough that you decided not to merge this code specifically? (Since you closed the pull request, but didn't actually merge) |
|
For anyone else wondering why they cannot actually use this feature, the configuration parameter is not |
|
I don't know about the changelog, but my commit log indeed says @apiPrivate. Now what I failed to do in time was to get the website documentation updated to include this parameter, but I've since put in a pull request for that and hopefully it'll be merged/rebuilt/deployed soon. |
|
What I am referring to is the following information:
However, internally, it uses the |
|
Ah, I see. Sorry for the confusion. I based it on the other command-line parameters, none of which prefaced with "api", but for the apidoc itself, all of them are prefaced with "api". Hopefully when the website documentation is updated, it'll be more clear. |
Added @apiPrivate to support the ability to specify
if an API is a private API. apidoc now also has a
--private false|true parameter on the command line
that defaults to false. If false, it does not include
any API block that contains @apiPrivate. If true, it
will include the API (assuming the API is also not marked
as @apiIgnore).