-
-
Notifications
You must be signed in to change notification settings - Fork 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
[FIX] table_to_frame: metas lost on conversion #4259
[FIX] table_to_frame: metas lost on conversion #4259
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4259 +/- ##
==========================================
+ Coverage 86.77% 86.81% +0.03%
==========================================
Files 396 396
Lines 71550 71557 +7
==========================================
+ Hits 62089 62121 +32
+ Misses 9461 9436 -25 |
Thank you for the PR. Some comments:
|
Hi, Vesna.
In my personal opinion this parameter can cause confusion in further usage, i believe by default table supposed to be transformed into frame without any columns lost. The user always can drop some columns explicitly if he needs. There might be some incompatibility though in case somebody rely on output frame columns number (maybe in tests). Otherwise i guess additional (in comparison with prev. results) datarfame columns shouldnt provide any harm to existing code. |
All that is true and I agree with you, but still, the existing code should not be broken. |
Or a year. Better. |
Decision at the meeting: @VesnaT implements what she proposed here and merges the PR. |
13a7bf7
to
4a9a063
Compare
4a9a063
to
8b2a8f5
Compare
Issue
Description of changes
Includes