-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
[docs] Document --enable-post-process-file #5301
Comments
https://openapi-generator.tech/docs/usage/ How are these not proper documentation? |
I challenge you to find documentation for, say, |
In the docs for the gradle plugin: https://github.com/OpenAPITools/openapi-generator/blob/master/modules/openapi-generator-gradle-plugin/README.adoc
So this sounds very generator specific. Looking at the source code, just about every generator is looking for its own environment variable. Here is processOpts from the AbstractJavaCodegen.
So the source code confirms the convention described in the gradle plugin doc. This took less than 30 min to track down. Id suggest forking/downloading the source code since it also contains all the .md files and you can do a text search across everything, docs and source code, to better understand what is happening. That's how I found this tidbit in the gradle plugin docs even though I never use gradle. So yes, that particular option isn't documented well since everywhere else it pretty much repeats the name of what it is rather than going in to detail on how to use it. Sounds like a good candidate for a pull request. My question would be: did you have a need to understand this cli option? There is plenty of documentation about how to get things done with openAPI generator. What specific thing are you trying to accomplish that doesn't seem to exist in the docs? |
Ok, so to find that, I'd have to guess that it would be referred to not as
This is not a resounding success, it is an abject failure on the part of the docs.
Obviously. |
Asking about a specific, poorly documented cli option is far more constructive than making a generalized FALSE statement that the tool has no proper documentation. The former is asking for specific help, or even pointing out a specific issue with docs. The latter is largely just a complaint without any details that serves absolutely no one. |
I too came looking for documentation on Not denying anyone's efforts here, just stating there's room for improvement here. |
Please follow community guidelines and be respectful and constructive. There's always room for improvement in documentation, but opening issues containing only a description of:
Is neither constructive or respectful. I spent maybe 80% of my efforts on this project last year putting together the documentation site at https://openapi-generator.tech, making it easier for developers to find information about the tool through the CLI, putting together multiple example repositories, and driving the adoption of our Slack community specifically for simple questions/asks such as these. Since we have a standard |
There is no proper documentation for this tool anywhere.
The text was updated successfully, but these errors were encountered: