-
-
Notifications
You must be signed in to change notification settings - Fork 634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Confusing warning "phpDocumentor supports 1 set of API documentation at the moment"
#3493
Comments
That is a really good question! When you use the command-line like you did, it should create a single set of API Documentation with these settings. It sounds like there is a bug there, though it probably also meant that you might have been missing some pieces of doc because this error only describes the existing assumptions in the application.. unless the error itself has a bug.. I'll check it out |
I think I found the cause, but I need to verify this in the code yet. If I remember correctly, there is a slight assumption in phpDocumentor that when you pass absolute paths as source directories, then it will assume they are not part of the same project and thus must be multiple individual Documentation Sets. I had trouble reproducing your situation until I started using absolute paths like this:
If I change that to
The issue does not occur. As such, I recommend using relative paths or a configuration file. What I can do in the mean time is to change the error message and/or documentation to make this clear |
I have just updated the error message with why the error occurs and how it can be resolved: e59fc6e I apologize for the inconvenience, it would have been handy if we had added this message when we started with the effort to support multiple documentation sets |
Thank you so much 😊 |
Seems to be added here: #3477, but without specifics about what exactly will cause this.
I have tried to go through the code and see what causes this exact error, but I can't identify anything.
We are running PHPDocumentor from a Dockerfile, with no extra config and it has been working perfectly until last week:
What are we doing wrong?
The text was updated successfully, but these errors were encountered: