-
Notifications
You must be signed in to change notification settings - Fork 204
Improve FencedCodeBlockSyntax #478
Improve FencedCodeBlockSyntax #478
Conversation
Pull Request Test Coverage Report for Build 3346469099Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
893c9b8
to
7c63754
Compare
@chenzhiguang – please rebase on If there are breaks there, we'll have to dig to see what's expected/intended. |
4129730
to
5f5a2ad
Compare
Rebased |
Can we have a look at this one? It is important to my next PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this all looks really good.
Would you mind posting benchmarks, before and after? I get ancy with RegExp changes. There are definitely strings that have really bad performance with some RegExp, and this has appeared in Flutter code before.
Just a few other requests.
@srawlins – I think benchmarks look fine, no? |
845f6d8
to
664d9a0
Compare
rebased |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
CC @devoncarew This one passes flutter_markdown 🎉 |
Cool, thanks! |
* Improve FencedCodeBlockSyntax * Update gfm_stats.txt * Fix some requests * run tool/stats.dart --update-files
Strictly improves the test coverage.