-
Notifications
You must be signed in to change notification settings - Fork 363
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
[Fix] Fix BaseDataPreprocessor.cast_data
cound not handle string data
#602
[Fix] Fix BaseDataPreprocessor.cast_data
cound not handle string data
#602
Conversation
Refine type hint
Codecov ReportBase: 77.91% // Head: 78.10% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #602 +/- ##
==========================================
+ Coverage 77.91% 78.10% +0.19%
==========================================
Files 126 126
Lines 9072 9039 -33
Branches 1806 1800 -6
==========================================
- Hits 7068 7060 -8
+ Misses 1691 1666 -25
Partials 313 313
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. |
# Conflicts: # mmengine/model/base_model/data_preprocessor.py
…ta (open-mmlab#602) * [Fix] Fix cound not handle string data * Minor refine * Refine type hint Refine type hint * fix as comment * Minor refine * Update mmengine/model/base_model/data_preprocessor.py Co-authored-by: Zaida Zhou <58739961+zhouzaida@users.noreply.github.com>
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
Fix
BaseDataPreprocessor.cast_data
cound not handle string data to solve #575Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repos?
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