-
Notifications
You must be signed in to change notification settings - Fork 17
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
Edge Cases Thread #24
Comments
whitespace/end-of-line rules in link destination:
|
link destinations should be case-insensitiveI couldn't find this in doc, but Neorg seems to be working like this.
|
What happens when we put carryover tag inside attached modifiers? Considering the precedence, should it break the attached modifier? Or as line-ending inside attached modifier can be ignored, carryover tag inside attached modifier is just invalid?
Similar precedence cases:
|
Does terminating slide with a paragraph break means it is only terminating that list item but not a whole list?
|
Anchor link inside anchor link
I think we can solve this edge case by converting to syntax sugar for wikilinks (automatically converted to |
Free form attached modifier inside headings
Cause |
Can
Does sometitle or someothertitle take precedence |
Extra: spec doesn't define what sort of objects are allowed after a single definition (only a paragraph? or any single complex object?) |
escape sequence can be used to escape non-punctuation character, is this intended behavior?
|
Injection to link location
Should spec disallow |
Structable's prefix inside attached modifiers?
If there is no following whitespace in line 2, this would be valid attached modifier, right? |
Since detached modifiers have a higher precedence than attached modifiers it becomes an unclosed |
Yep, it is! It's for the sake of consistency. It won't do anything, in fact it will just return an |
All the Edge Cases
The specification isn't perfect, and as such this thread exists for any other parser writers to ask questions or note inconsistencies/ambiguities in the spec.
cc @boltlessengineer :D
The text was updated successfully, but these errors were encountered: