-
Notifications
You must be signed in to change notification settings - Fork 217
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
TableCaption Node's start/end indices are not set #175
Comments
You rock! :) |
fix Escaped Characters for disabled extensions sirthias#179 add StrikeNode has isClosed() member sirthias#178 fix Reference node includes trailing blank lines sirthias#177 fix Setext headers not allowing blanks after --- or === sirthias#176 fix CaptionNode not having source index range set sirthias#175 add ATXHEADERSPACE extension to require a space/tab after # in AtxHeaders sirthias#144 add RELAXEDHRULES extenstion to relax requirement of a blank line after horiz. rule. sirthias#129 fix STRIKETHROUGH extension did not add ~ to special characters. sirthias#131
fix Definition Lists sirthias#180 fix Escaped Characters for disabled extensions sirthias#179 add StrikeNode has isClosed() member sirthias#178 fix Reference node includes trailing blank lines sirthias#177 fix Setext headers not allowing blanks after --- or === sirthias#176 fix CaptionNode not having source index range set sirthias#175 add ATXHEADERSPACE extension to require a space/tab after # in AtxHeaders sirthias#144 add RELAXEDHRULES extenstion to relax requirement of a blank line after horiz. rule. sirthias#129 fix STRIKETHROUGH extension did not add ~ to special characters. sirthias#131
Closed by #181. |
Thank the plugin. Visually highlighting the range makes finding bugs a piece of cake. I now have a “Debug” scheme in the plugin for myself. It has neon background colours for all the elements so that you can easily see where they start and end. Best regards, Vladimir.
|
The TableCaption node is not properly created in the parser resulting in startIndex, endIndex always being zero.
I have a fix and an AST test, here is the result of the new AST test without the fix, it shows the problem well:
Will post PR with a bunch of other parser compatibility and other source range anomalies.
The text was updated successfully, but these errors were encountered: