Skip to content

Inline-link target proposal #25

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

Closed
wants to merge 6 commits into from
Closed

Inline-link target proposal #25

wants to merge 6 commits into from

Conversation

mrossinek
Copy link
Member

@mrossinek mrossinek requested a review from vhyrro January 15, 2022 22:52
@mrossinek mrossinek self-assigned this Jan 15, 2022
Comment on lines +182 to +194
$.inline_link_target_open,
$.inline_link_target_close,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is slightly inconsistent right now:

  • attached markup is generally treated like this
  • BUT: link descriptions and texts are not treated the same way...
  • this is somewhat inbetween. How shall we unify this?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will be unified when specifying the formal spec in #29. Generally speaking, link objects {}, [], and <> form there own category and should not be treated like attached modifiers.

@mrossinek mrossinek force-pushed the inline-link-targets branch from 5548848 to 4e71625 Compare January 22, 2022 13:03
@mrossinek
Copy link
Member Author

Superseded by #35

@mrossinek mrossinek closed this Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants