Invalid elements in markdown files silently creates invalid HTML #154

New issue

Closed

opened 2018-09-24 23:25:12 +02:00 by kauffj · 0 comments

kauffj commented

2018-09-24 23:25:12 +02:00

(Migrated from github.com)

partialFinder in redirect.js silently skips custom partials that it cannot find a corresponding component file for.

However, some part of the markdown processing chain will still process these elements and as a result it will create invalid markup.

Inserting a random fake element in a markdown file like <DidThisInsertAnInvalidTagInMyHTML /> will reproduce this issue.

`partialFinder` in `redirect.js` silently skips custom partials that it cannot find a corresponding component file for. However, some part of the markdown processing chain will still process these elements and as a result it will create invalid markup. Inserting a random fake element in a markdown file like `<DidThisInsertAnInvalidTagInMyHTML />` will reproduce this issue.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry.tech#154

No description provided.