-
Notifications
You must be signed in to change notification settings - Fork 12
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
Audit the intra-doc links to find breakage #112
Comments
tzlaine
added a commit
that referenced
this issue
Feb 24, 2024
Ok, so apparently you can add an empty file called |
tzlaine
added a commit
that referenced
this issue
Feb 26, 2024
tzlaine
added a commit
that referenced
this issue
Mar 2, 2024
tzlaine
added a commit
that referenced
this issue
Mar 2, 2024
tzlaine
added a commit
that referenced
this issue
Mar 2, 2024
tzlaine
added a commit
that referenced
this issue
Mar 2, 2024
tzlaine
added a commit
that referenced
this issue
Mar 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There were a bunch of broken links reported in the Boost review. They were all
_foo()
functions (e.g._val()
). Each of these ends up in its own Doxygen-generated file, likeparser/doc/html/boost/parser/_val.html
. Problem is, the Github Pages publishing software won't process those files, because of the leading underscore. So this should have no impact on the final docs on the Boost website. I claim victory. Also, while auditing all the links, I did find a real broken one, to the "Expectation points" section. So that still needs fixing.The text was updated successfully, but these errors were encountered: