-
Notifications
You must be signed in to change notification settings - Fork 11
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
473 na strings #474
473 na strings #474
Conversation
Sorry, at my first coffee this morning, will this modify the behavior aside from replacing missing? Aka if I want to write "N/A", do I have to write Or is this just something like our flavor of |
More Lines 311 to 330 in 2a8dbaf
|
Thanks, it was just for my understanding. I'll review it after the release. Should be harmless and I prefer it the way it is, but I don't have the time and focus right now. One thing at the time :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Since
na_strings()
will be visible to the user, we should have a manual entry. - Minor
lintr
issues - Maybe update NEWS for the argument change?
- Add this as a default for
wb_to_df()
as well? So that the user has a clean interface? Something likewb_to_df(..., na.strings = na_strings()) { ..., if (is_na_strings) na.strings <- "#N/A")
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me. What about my previous comment:
* Add this as a default for `wb_to_df()` as well? So that the user has a clean interface? Something like `wb_to_df(..., na.strings = na_strings()) { ..., if (is_na_strings) na.strings <- "#N/A")`.
@jmbarbone Please let me know what you intend to do with these patches. I like this |
@JanMarvin , sorry, lost track of this. I've made a few more edits and it looks like everything is running fine after merging in |
Thanks, I'll have a look tomorrow. |
Thank you, I have merged this PR. Looks nice :) But please, before you start updating #471, I still haven't made up my mind about the size and impact of the PR and would veto the merge at this point. I still feel that the risk of breaking things along the way still outweighs the benefit of having more organized (and possibly cleaner) code. Since I started porting some real life work over to Maybe we can break #471 into smaller pieces (e.g. not including the unnecessary |
resolves #473
A much cleaner PR. Nothing in the tests has to be changed for this to work.
Documentation would need to be updated if we wanted to go through with this. Happy to wait until a later release.