Skip to content
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

Parse inlineLink incorrectly if the link text is an URL #358

Closed
hoducha opened this issue Oct 24, 2015 · 4 comments
Closed

Parse inlineLink incorrectly if the link text is an URL #358

hoducha opened this issue Oct 24, 2015 · 4 comments

Comments

@hoducha
Copy link

hoducha commented Oct 24, 2015

Test data:

[http://example.com](http://example.com)

Expected result:

<a href="http://example.com">http://example.com</a>

Actual result:

<a href="http://example.com"><a href="http://example.com">http://example.com</a></a>
@petermolnar
Copy link

This could be the reason behind erusev/parsedown-extra#77

@francisbesset
Copy link

@petermolnar This issue can be reproduced with parsedown only.

This was referenced Oct 1, 2016
aidantwoods added a commit to aidantwoods/parsedown that referenced this issue Oct 1, 2016
1. Add the ability for a parsed element to enforce that the line handler not parse any (immediate) child elements of a specified type.
2. Use 1. to allow parsed Url elements to tell the line handler not to parse any child Links or Urls where they are immediate children.
@aidantwoods
Copy link
Collaborator

aidantwoods commented Oct 1, 2016

I've made a pull request #433 to address this issue

@cebe cebe mentioned this issue May 18, 2017
aidantwoods added a commit that referenced this issue Feb 28, 2018
Fix Issue #358 – preventing double nested links
@aidantwoods
Copy link
Collaborator

Fixed in #433

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants