-
Notifications
You must be signed in to change notification settings - Fork 32
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
docs: Fix basic rst formatting errors #2958
Conversation
The remaining 20 issues causing "problematic" are in the following files:
|
This PR causes the following changes to the html docs (ubuntu-latest-3.11):
See CI logs for the full diff. |
The HTML documentation with the fixes is available at [0] [0] https://jvesely.github.io/PsyNeuLink/branch/docs/ |
Fixes 3 instances of: WARNING: Malformed table. Signed-off-by: Jan Vesely <[email protected]>
Fixes 13 instances of: WARNING: Title underline too short. Signed-off-by: Jan Vesely <[email protected]>
Fixes 31 instances of: WARNING: Inline strong start-string without end-string. There are 6 remaining instances that all come from: psyneulink.core.scheduling.condition imported from graph_scheduler Signed-off-by: Jan Vesely <[email protected]>
Fixes one instance of: WARNING: Inline literal start-string without end-string. Signed-off-by: Jan Vesely <[email protected]>
Fixes two instances of: WARNING: Inline emphasis start-string without end-string. The remaining instances are imported from schedulin.condition. Signed-off-by: Jan Vesely <[email protected]>
Fixes 3 instances of: WARNING: Unknown target name: Signed-off-by: Jan Vesely <[email protected]>
Fixes 31 instances of: WARNING: Inline interpreted text or phrase reference start-string without end-string. Signed-off-by: Jan Vesely <[email protected]>
Fixes one instance of: WARNING: Inline substitution_reference start-string without end-string. Signed-off-by: Jan Vesely <[email protected]>
This PR causes the following changes to the html docs (ubuntu-latest-3.11):
See CI logs for the full diff. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
I'll try to fix the problems with build/html/Condition.html
.
Did you notice these just looking through the warning messages on a build or did you see the missing table in the docs?
Thank you. I didn't find a way to selectively turn some warnings into errors to prevent reintroducing them later. The current warnings count is:
|
Fix the following warnings:
WARNING: Malformed table. (3 instances)
WARNING: Title underline too short. (13 instances)
WARNING: Inline strong start-string without end-string. (31 instances)
WARNING: Inline literal start-string without end-string. (1 instance)
WARNING: Inline emphasis start-string without end-string. (2 instances)
WARNING: Unknown target name (3 instances)
WARNING: Inline interpreted text or phrase reference start-string without end-string. (31 instances)
WARNING: Inline substitution_reference start-string without end-string. (1 instance)
The above removes 61/81 instances of
<span class="problematic">
in the generated html.