-
Notifications
You must be signed in to change notification settings - Fork 735
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
Use function documentation script #6897
Conversation
Do we want to include private functions in the public docs? |
Yes, should be written like so:
Maybe we can skip that requirement.
No, and they are already filtered out when generating the docs (without |
56 errors left to fix. CI will fail if errors present. Private functions are no longer checked (separated debug and lint private options). |
I'll try to fix atleast some errors on weekend. |
From the looks of things, quite a few of them are functions that should be private |
@dedmen did you do anything on this? |
I don't even remember this. |
9684734
to
97d8b72
Compare
2747dc7
to
8f2a125
Compare
Only 18 errors left! |
Work from file dir back to addons
acb1693
to
8f4da94
Compare
@Dahlgren Please don't force push! One last error remaining:
I think the example in this function is wrong. Or the arguments is wrong and first parameter is actually array. If former, we should probably just add support for either no number in front of argument or |
Support starting from root or subfolder Read component name from script_component.hpp's COMPONENT_BEAUTIFIED for use in generated frontmatter title Add frontmatter for Jekyll Specify encoding for file operations
This is finally done!
|
When merged this pull request will:
TODO:
TODO (can be split to separate PR):
(we'll want to run it for ACEX as well, so 2 buttons)?