Monorepo for Tangled tangled.org

appview/pages : fix handle parsing false-positives #905

merged
opened by regnault.dev targeting master from regnault.dev/core: issue/333
0
by regnault.dev 0 comments
expand 1 commit
appview/pages : fix handle parsing false-positives
sign up or login to add to the discussion
1
by regnault.dev 0 comments
expand 1 commit
appview/pages : fix handle parsing false-positives
sign up or login to add to the discussion
2
by regnault.dev 0 comments
expand 1 commit
appview/pages : fix handle parsing false-positives
sign up or login to add to the discussion
3
by regnault.dev 5 comments
expand 1 commit
appview/pages : fix handle parsing false-positives

i have created https://tangled.org/tangled.org/core/pulls/910 to handle false positives, along with some tests. are there any cases that this PR handles and the other one does not? note that the linkify extension (provided by extensions.GFM) should run before the atlink extension for the test cases to work.

i can't say i am too familiar with the atlink extension (or goldmark extensions for that matter), @boltless.me would be the right person to review this code.

Yours seems to work with my test readme, I'll close this PR

Wait no, i'm studid, there's two cases that aren't taken into account in your branch:

[
@regnault.dev](https://regnault.dev)

[@regnault.dev](https://regnault.dev)

those are both great cases! i wonder if we are barking up the wrong tree by implementing this as a unique node, instead of having a pass at the html generation stage.

i say we keep this, but ill also incorporate my PR with the updated regex + tests!

pull request successfully merged
sign up or login to add to the discussion
Labels

None yet.

assignee
boltless.me
Participants 2
AT URI
at://did:plc:fs3xpvrweneqrjgr7v2oow62/sh.tangled.repo.pull/3mahojtfoym22