-
Notifications
You must be signed in to change notification settings - Fork 416
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
Character Error Rate #575
Character Error Rate #575
Conversation
Character Error Rate logic updated
for more information, see https://pre-commit.ci
Codecov Report
@@ Coverage Diff @@
## master #575 +/- ##
=====================================
Coverage 95% 95%
=====================================
Files 146 148 +2
Lines 5052 5108 +56
=====================================
+ Hits 4807 4861 +54
- Misses 245 247 +2 |
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.
So the implementation is already looking great :]
Missing
- tests
- bindings in
__init__
files - sections in documentation
- entry in CHANGELOG
Co-authored-by: Jirka Borovec <[email protected]>
Co-authored-by: Jirka Borovec <[email protected]>
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
@Borda @SkafteNicki , there are 7 workflows awaiting approval. please check and review |
@SkafteNicki , pytest with (ubuntu-20.04, 3.9, latest) and pytest (windows-2019, 3.8, minimal) cancelled 10/12 - successful, 2/12 cancelled |
shall be fixed now on master... the case is that the newest PT 1.10 takes much longer than others... |
@Borda @SkafteNicki please review and let me know, if any changes need to be updated from my end |
for more information, see https://pre-commit.ci
Hi @mahinlma, PR is overall looking really good. |
Character Error Rate logic updated
Before submitting
What does this PR do?
Fixes # (issue).
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃