-
-
Notifications
You must be signed in to change notification settings - Fork 362
docs: Fix Doxygen warnings due to invalid docstring syntax or missing tags #6097
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
Conversation
Locally, I was redirecting the console output into two separate files for stdout and stderr, as all the warnings and problems to fix are found in the stderr. And the output had more lines than my scroll buffer I was using something like
|
Clang (at least) have the
I used it extensively a few years ago fixing GEOS docs. |
Interesting! I’ll for sure try it out, but at least Doxygen, even on the older version, is still able to spot a lot. And with VS code, since it is a full path+line number+column number, I can just CTRL+click and get directly to the place to fix. I didn’t have that much luck with a compiler output yet, as we usually use relative commands from makefiles |
Co-authored-by: Anna Petrasova <[email protected]>
Similar to the bunch of fixes I did with sphinx in the last months or so, here is a first PR solving Doxygen warnings that can now be seen in CI (since #6092).
It is a first batch with what I have yet, no particular grouping expect at the commit level.
There’s still lots of the same categories, it’s only what I had done yesterday.