-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[CodeCamp #99] type hints Part C #1604
Conversation
Codecov ReportBase: 87.91% // Head: 87.92% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## dev-1.x #1604 +/- ##
===========================================
+ Coverage 87.91% 87.92% +0.01%
===========================================
Files 399 399
Lines 26024 26050 +26
Branches 4048 4048
===========================================
+ Hits 22879 22905 +26
Misses 2240 2240
Partials 905 905
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
* [Refactor] Refactor fileio * fix ut * fix self.backend_args * fix self.backend_args * fix self.backend_args * fix self.backend_args * fix vis_backend * fix vis_backend * fix vis_backend * fix vis_backend * fix vis_backend * fix ut
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
Who can help? @ them here!
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist
Before PR:
After PR: