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
Formatting of declarator blocks in subroutine's parameters #18
Comments
Edit: the output is so weird I completely misread it. 😄 The name is there, as @uzluisf says, it's just difficult to see. |
Thanks for this bug report. I think my reason for this was to copy the way Pod::To::HTML behaved at the time. This should be revised. I welcome any patches should you get to it before I do. |
Unfortunately, it appears that fixing this requires a (major?) fix to rakudo. The contents of
I can't think of a hack to fix this in the short term. Long term I'm sure there are bugs open in rakudo for this, but I don't know which. I'd appreciate anyone linking relevant rakudo bugs here. |
I've raised a Rakudo ticket |
Declarator blocks (
#=
) for a subroutine's parameters are formatted as H2-level headings while the subroutine's name is formatted as H3-level heading. This makes them seem out of place. Ideally, the subroutine's name would be formatted with a heading level higher than anything else that belongs to it.Example: https://gist.github.com/uzluisf/ec9fa34e603bdc11d5e84642e6d74ddc
The text was updated successfully, but these errors were encountered: