-
Notifications
You must be signed in to change notification settings - Fork 487
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
Markdown.Paragraph might not contain an array #1708
Comments
The Markdown AST generated by CBinding.jl is, by some definition, invalid. I don't think the parser ever generates AST where the children would not be wrapped in a But you're right in that the Documenter.jl/src/Utilities/Markdown2.jl Line 227 in bffc866
|
Better yet might be to silently "promote" it to a 1-element Vector if it is not already a Vector. It appears that something similar is already being done in other situations: Documenter.jl/src/Utilities/Markdown2.jl Line 265 in bffc866
|
@mortenpi I tested this again with Documenter v1.1.0, seeing a similar traceback as before, see analytech-solutions/CBinding.jl#89 (comment). I think it is related, but not the same error? |
In reference to analytech-solutions/CBinding.jl#89
Documenter doesn't accept
Markdown.Paragraph(Markdown.Link(...))
even though it renders in the REPL help mode correctly. It seems that the contents of the paragraph are assumed to be an array, but there is no type restriction on the field to enforce that. Indeed, Documenter works when making a change to meet that assumption (Markdown.Paragraph([Markdown.Link(...)])
.The text was updated successfully, but these errors were encountered: