v0.9.4
This was a point release that highlighted improvements to the accuracy of reported tokens
in situations with nested containers.
- Removed "call home support" similar to VSCode and other products.
- One of our contributors pointed out a number of fallacies, and we agreed.
- Enhanced testing of the whitespace calculations recently completed.
PLEASE! If you encounter any issues with this product, please file an issue report and tell us about it!
There are a lot of combinations of Markdown elements to cover, and we need your help to prioritize them all!
Changed
- Changed - Issue 184
- scenario tests: instead of mixup in different areas, added initial combinations to test in one place
- Changed - Issue 207
- adding more upfront analysis, upgrading Columnar to new version
- Changed - Issue 214
- removing call home support
Fixed
- Fixed - Issue 159
- parser: was using wrong values to determine nesting level
- Fixed - Issue 185
- parser: nesting of block quote, list, block quote raised an assert
- Fixed - Issue 186
- parser: due to work on Issue 187, these now passed after assert examine and disabled
- Fixed - Issue 187
- parser: three separate adjustments needed to be made to ensure the whitespace is consistent
- Fixed - Issue 188
- parser: not dealing with a block occurring after 2 nested lists
- Fixed - Issue 192
- parser: needed to adjust
__calculate_current_indent_levelfunction to accommodate nesting
- parser: needed to adjust
- Fixed - Issue 196
- markdown: transformer was not calculating indent properly
- Fixed - Issue 197
- parser: block quote processor was not closing blocks properly, resulting in bad HTML
- Fixed - Issue 198
- markdown: algorithm was not taking into effect newer change to calculate container indices later
- Fixed - Issue 199
- parser: fixed by work done on Issue 202
- Fixed - Issue 200
- markdown: calculation for previous indent and whitespace to add after was off
- Fixed - Issue 201
- parser: fixed by work done on Issue 202
- Fixed - Issue 202
- parser: block quote processor needed a lot of work to handle whitespace properly
- parser: container block processor not handling 4 spaces at start of line properly
- Fixed - Issue 203
- markdown: adjustments to properly calculate indent
- parser: list block processor not transferring extracted text to a nested block
- various cleanup
- Fixed - Issue 219
- parser: indents of 4 within a single and double level list were not cleanly differentiating