OneHotEncoder Preserves Custom Index #1146
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## main #1146 +/- ##
=======================================
Coverage 99.91% 99.91%
=======================================
Files 195 195
Lines 11506 11515 +9
=======================================
+ Hits 11496 11505 +9
Misses 10 10
Continue to review full report at Codecov.
|
freddyaboulton
requested review from
angela97lin,
eccabay,
dsherry,
bchen1116 and
jeremyliweishih
jeremyliweishih
approved these changes
Sep 8, 2020
freddyaboulton
force-pushed
the
1074-ohe-introduces-nans-custom-index
branch
4 times, most recently
from
effc79b
to
d59f91d
Compare
freddyaboulton
force-pushed
the
1074-ohe-introduces-nans-custom-index
branch
from
d59f91d
to
0e413d6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Description
Fixes #1074.
After creating the pull request: in order to pass the release_notes_updated check you will need to update the "Future Release" section of
docs/source/release_notes.rstto include this pull request by adding :pr:123.