Skip to content

Incorrect link handling #14

Description

@thomasheartman

Orga doesn't appear to handle links in definition lists, and also does not apply the correct formatting if a link is formatted as source code using the ~ character.

I appreciate that these are two separate issues, but I hope you don't mind me opening them together, as the images show both issues.

Expected outcome

  1. When using links in definition list headers, I expect them to render as links.
  2. When using a link in text surrounded by ~ characters, I expect it to be rendered in a <code> tag.

As a visual, I expected the rendered text to look like this (as rendered by Pandoc and Hakyll):
image

Notice the definition list 'header', and the two links at the end of the paragraph, Maybe and Either

Actual outcome

  1. Links in definition lists are not rendered or even picked up on properly. They render as plain text.
  2. Links that should be formatted as <code> are not, and are instead just surrounded by ~ characters in the rendered HTML output.

Here's what Orga and Gatsby renders:
image

In this image, the header is rendered as the literal link text content in org mode and is not a link. The two links at the end are surrounded by ~ characters and are not in <code> tags.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions