Closed yshavit closed 3 months ago
whether this should apply to all inline code text, or just
`
How do you mean? Isn’t all “inline code” / “code (text)” with `
?
whether I should adjust the position fields (and if so, which? all of them, or just the *_offsets?) to account for the stripping the spaces
I don’t think that’s needed. Positional info represents the whole, which includes the backticks too. So the spaces have no effect on it.
apologies if this PR is not the appropriate way to do that!
This is great! Thank you!
whether this should apply to all inline code text, or just
`
How do you mean? Isn’t all “inline code” / “code (text)” with
`
?
I think this the raw_text also covers $$
, but I'm not 100% — I haven't tested it out yet. And I'm also not sure whether $$
also requires stripping the space.
whether I should adjust the position fields (and if so, which? all of them, or just the *_offsets?) to account for the stripping the spaces
I don’t think that’s needed. Positional info represents the whole, which includes the backticks too. So the spaces have no effect on it.
Awesome, thanks! That makes it easy.
apologies if this PR is not the appropriate way to do that!
This is great! Thank you!
Glad to hear it! 😁
Unfortunately, I won't be able to get to it until later tonight (US east coast), but I'm guessing there's no urgency on this from your end. :-)
$
, as in math, has no standard. I intentionally here use the exact same working of `
for $
. So :+1: to same workings for both.
No urgency from me! I really appreciate you helping!
Ah, if they intentionally work the same, then perhaps this PR is ready to go? I'll go ahead and mark it as "ready for review" and subject it to full critique! :-)
Awesome, thanks so much!
Strip one space from the beginning and end of InlineCode if (a) the value starts and ends with a space and (b) is not all spaces.
From CommonMark spec section 6.1:
Resolves #122