Add API Blueprint exclude option

[frthjf]

I think it would be helpful, if you could exclude Api Controllers from the documentation through some directive, maybe @Ignore.

[hskrasek]

@dudheit Could be useful, wouldn't you want to document all of your API Endpoints though?

[frthjf]

Eventually yes. However, I was facing the following situation:
I developed an API for an intranet application with serveral controllers to manipulate different resources. The API included a UsersController as well, which allowed to adminstrate the users of the application.
However, this user API endpoint was for an external application only. So the users were managed in a different application, which then updated the users information through the intranet app API accordingly. Therefore, the UserController was protected by a special middleware.
When I tried to generate the API docs, Dingo threw an exception as it couldn't access the controller function.
Now what I did was commenting out the middleware in order to generate the API docs for the actual intranet application and that made me thinking whether an ignore option would be a better option.
Maybe, on the other hand, it might be a better idea to let Dingo deal with protected endpoints, I am not sure.

So just provide some details: Auth::guard('api')->user()->id invoked a Trying to get property of non-object exception, stopping the docs generation.