Closed IlyaMatsuev closed 1 year ago
Hi @IlyaMatsuev
That totally makes sense, and I agree. I think I rather make it the default to not include that info, and have a flag to optionally include it, cause I agree that is a rare use case, and skipping having to read the .xml file could have a positive performance impact. Could be a breaking change for some but I honestly wonder how many people would care.
Let me look into this
Cool, thanks for the quick feedback
Available in 2.14.0 https://www.npmjs.com/package/@cparra/apexdocs/v/2.14.0. Let me know if anything could be improved or is not working
Hi, Thanks for creating this CLI, it helps a lot. However, I have a suggestion about what's being printed in the .md file for an Apex class. Doesn't matter what options and generators I use, I always get ApexClass meta information in the final markdown file. I don't really see much sense in printing this information as I've never seen in that somebody would expose and not delete an Apex class with
Status: Inactive
. ApexClass API version is a bit more important but again, most of the time it's not required for a user to know the exact API version.So, would it be possible to have at least a CLI option to disable that ApexClass meta information to be printed?
What I'm running:
Example source file:
Expected result .md file:
Actual result .md file: