docs: Fixed jsdoc generation by marking private methods as @private #1976
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I noticed after refactoring message-shim and webframework-shim the API docs were not being properly generated.
One issue was the WebFrameworkShim and MessageShim docs are gone, this was because they are now subdirectories. But there was also a lot of global functions. This PR marks all private methods as such in jsdoc with
@private
, but also fixes thepublic-docs
script to include the new subdirectories of the shim files.How to Test
It should have MessageShim and WebFrameworkShim in the Classes section. Also the global section should remove a lot of private functions.