-
Notifications
You must be signed in to change notification settings - Fork 985
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
add message that datatable.nomatch will be deprecated #3612
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3612 +/- ##
==========================================
+ Coverage 97.81% 97.81% +<.01%
==========================================
Files 66 66
Lines 12927 12929 +2
==========================================
+ Hits 12645 12647 +2
Misses 282 282
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #3612 +/- ##
=======================================
Coverage 98.19% 98.19%
=======================================
Files 66 66
Lines 12922 12922
=======================================
Hits 12689 12689
Misses 233 233
Continue to review full report at Codecov.
|
Not sure if you saw my earlier comment here : #3578 (comment). This would allow us to not introduce the new |
Yes, but it is less trivial, and need message about |
Yes deprecating nomatch option would need time and communication, and a message would be first step.
Do you mean you agree with my suggestion to use |
I agree but I don't want to include that in this PR. It would be good to have it in separate PR. This would be API change and once users will start to use it will be difficult to amend changes to it. |
Closes #3585 (revised)
First step is to inform and communicate.