Skip to content

Conversation

@robinst
Copy link
Collaborator

@robinst robinst commented Oct 24, 2022

With the previous version we adjusted the extension to also accept the single tilde syntax. But if you use another extension that uses the single tilde syntax, you will get a conflict, see issue.

To avoid that, StrikethroughExtension can now be configured to require two tildes like before, see Javadoc.

With the previous version we adjusted the extension to also accept the
single tilde syntax. But if you use another extension that uses the
single tilde syntax, you will get a conflict, see issue.

To avoid that, `StrikethroughExtension` can now be configured to require
two tildes like before, see Javadoc.
@codecov-commenter
Copy link

codecov-commenter commented Oct 24, 2022

Codecov Report

Merging #272 (6db2990) into main (ba673a9) will increase coverage by 0.01%.
The diff coverage is 88.23%.

@@             Coverage Diff              @@
##               main     #272      +/-   ##
============================================
+ Coverage     94.24%   94.26%   +0.01%     
- Complexity      232      234       +2     
============================================
  Files           124      124              
  Lines          3631     3642      +11     
  Branches        550      550              
============================================
+ Hits           3422     3433      +11     
- Misses          104      105       +1     
+ Partials        105      104       -1     
Impacted Files Coverage Δ
...ough/internal/StrikethroughDelimiterProcessor.java 90.90% <66.66%> (-9.10%) ⬇️
.../ext/gfm/strikethrough/StrikethroughExtension.java 100.00% <100.00%> (ø)
...mmonmark/internal/StaggeredDelimiterProcessor.java 93.75% <100.00%> (+6.25%) ⬆️

@robinst robinst merged commit 376fc8e into main Oct 27, 2022
@robinst robinst deleted the issue-271-strikethrough-two-tildes branch October 27, 2022 00:23
@laurentpellegrino
Copy link

laurentpellegrino commented Nov 12, 2022

@robinst Thanks for adding this option!

Would you mind making a release that includes the changes?

@robinst
Copy link
Collaborator Author

robinst commented Nov 17, 2022

@lpellegr Released 0.21.0 with these changes now :)

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.

4 participants