[BUG] Entering new metadata rows breaks parsing
CompletedPretty minor problem, but when keying in a new metadata row, so that the new entry is inserted between existing rows, the parsing engine will cease considering everything below the inserted row to be metadata. While this make sense until one types in enough text to once again have a cohesive and valid metadata block, the problem I am reporting is that the formatting does not "heal" once it has reached that point:
1. In a new test note, copy and paste the following metadata example lines and content:
```
Title: Test Metadata Entry
Date: 2019-05-31
Keywords: nvUltra-20;beta
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
```
2. Place the cursor at the end of the Date line and press Return.
The Keywords line should start rendering as normal text. Again this is expected behaviour because at this point the following line *is* regular text, given the syntax rules.
3. Type in `Author: Beta Tester`
Everything below that point will stay printed as normal text, until reloading the note in the editor, even once you've typed in enough for this line to be considered correct syntax for a metadata line. (It's worth noting Composer 4 considers the following lines to be metadata the moment you hit "A" on the new line.)
This problem does not happen when using copy and paste to insert an existing metadata line.
0
-
Fixed for next release.
Thanks!
0
Please sign in to leave a comment.
Comments
1 comment