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
publishToConfluence looses the id when generating level 2 page anchors #1161
Labels
Comments
srotman
pushed a commit
to srotman/docToolchain-1161
that referenced
this issue
May 9, 2023
srotman
added a commit
to srotman/docToolchain
that referenced
this issue
May 9, 2023
srotman
added a commit
to srotman/docToolchain
that referenced
this issue
May 9, 2023
srotman
added a commit
to srotman/docToolchain-1161
that referenced
this issue
May 9, 2023
srotman
added a commit
to srotman/docToolchain-1161
that referenced
this issue
May 9, 2023
Would be fixed by #1162 |
5 tasks
PacoVK
added a commit
that referenced
this issue
May 12, 2023
…removal Record page anchor before header removal. fixes #1161
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using the
subpagesForSections=2
setting, Confluence will loose the links to level 3 adoc headersTo Reproduce
Steps to reproduce the behavior:
concluence.with
setting forsubpagesForSections
to 2Expected behavior
The pageAnchors are not lost, and the links on the published Confluence page work :-)
Configuration
Additional context
I created a minimal example containing this issue: https://github.com/srotman/docToolchain-1161
According to my analysis, the problem lies in the
getPagesRecursive
function:docToolchain/scripts/asciidoc2confluence.groovy
Lines 944 to 958 in c9cc6f3
It seems that the
new Elements(...)
constructor (line 949) does not perform a deep Copy, resulting in a removal of the h3 element on line 950. The subsequent select of that same element on line 958 now yields no results any longer.If this line:
docToolchain/scripts/asciidoc2confluence.groovy
Line 958 in c9cc6f3
The text was updated successfully, but these errors were encountered: