Switch APM Agent for NodeJS to Asciidoctor - #724
Merged
Conversation
Switches the core of the docs build process from the no-longer-maintained AsciiDoc to the actively-maintained Asciidoctor. The resulting HTML is mostly the same but there are a few differences: 1. Spacing changes that the browser ignores 2. AsciiDoc adds `<p></p>` inside any empty table cell. Asciidoctor does not. 3. The automatically generated alt text for one of the images is different in Asciidoctor. I believe the Asciidoctor alt text is marginally better but I don't think automatically generated alt text is a good thing in general. 4. There is a particular table cell that seems to be changed like so: - ^2.0.0 || ^3.1.0 + \^2.0.0 || ^3.1.0 I think we can probably change the table cell in the docs after merging Asciidoctor. 5. One of the deprecation warnings looks a little sad: - Span started automatically by - <a class="link" href="agent-api.html#apm-start-span" title="apm.startSpan([name][, type])"> - apm.startSpan() - </a> + Span started automatically by <<apm-start-span I'm going to investigate this one further before we merge this. I expect Asciidoctor has a non-greedy regex instead of a greedy one. We might just have to work around this. This seems to be a rare thing. But I'll check!
Member
Author
|
Here is the difference: https://gist.github.com/nik9000/b710efd273a0282bfb8c888696da3d87 |
Member
7 tasks
Member
Author
|
I worked around 5 by doing this: |
Member
Member
|
Edit: nope, this doesn't work |
bmorelli25
approved these changes
Mar 15, 2019
bmorelli25
left a comment
Member
There was a problem hiding this comment.
LGTM pending elastic/apm-agent-nodejs#923
Member
Author
That doesn't render right for me in Asciidoctor. I think we might have hit something that is incompatible between the two. My fix works for Asciidoctor only and looks wrong in Asciidoc. Yours looks wrong in Asciidoctor.... |
Member
|
Good call, I was testing with asciidoc still on accident 🤦♂️ . Updated my comments above, and fixed the Node PR to something that works with asciidoctor. |
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Switches the core of the docs build process from the
no-longer-maintained AsciiDoc to the actively-maintained Asciidoctor.
The resulting HTML is mostly the same but there are a few differences:
<p></p>inside any empty table cell. Asciidoctor doesnot.
different in Asciidoctor. I believe the Asciidoctor alt text is
marginally better but I don't think automatically generated alt text is
a good thing in general.
I think we can probably change the table cell in the docs after merging
Asciidoctor.
5. One of the deprecation warnings looks a little sad:
I'm going to investigate this one further before we merge this. I expect
Asciidoctor has a non-greedy regex instead of a greedy one. We might
just have to work around this. This seems to be a rare thing. But I'll
check!