We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We could try to detect unresolved links in the documentation, and warn the user about them.
A simply approach would be to scan the finaly HTML files for <span class="RefLink">???</span> (at least for packages using GAPDoc).
<span class="RefLink">???</span>
Another would be to scan the GAPDoc output, looking for WARNING: non resolved reference.
WARNING: non resolved reference
Not sure how to deal with gapmacro output, but there is probably also a tell tale one could search for.
The text was updated successfully, but these errors were encountered:
makedoc.g
This was done in PR #84 for GAPDoc based manuals.
Sorry, something went wrong.
No branches or pull requests
We could try to detect unresolved links in the documentation, and warn the user about them.
A simply approach would be to scan the finaly HTML files for
<span class="RefLink">???</span>
(at least for packages using GAPDoc).Another would be to scan the GAPDoc output, looking for
WARNING: non resolved reference
.Not sure how to deal with gapmacro output, but there is probably also a tell tale one could search for.
The text was updated successfully, but these errors were encountered: