Skip to content

stat_bin2d now handles NA in data#448

Closed
BrianDiggs wants to merge 2 commits intotidyverse:masterfrom
BrianDiggs:fix/stat-2d-scale-range
Closed

stat_bin2d now handles NA in data#448
BrianDiggs wants to merge 2 commits intotidyverse:masterfrom
BrianDiggs:fix/stat-2d-scale-range

Conversation

@BrianDiggs
Copy link
Contributor

stat_bin2d did not correctly handle NA's in the data. This could be
triggered by setting scale limits which did not include the entire
range of the data.

This arose from a discussion on the mailing list
https://groups.google.com/d/topic/ggplot2/VAB1wKqwg9w/discussion

stat_bin2d did not correctly handle NA's in the data. This could be
triggered by setting scale limits which did not include the entire
range of the data.
R/stat-bin2d.r Outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you mind putting spaces around = please?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And I was trying to be careful to follow your style too. Fixed this in another commit, as well as others in the same file.

Both the code I added and existing code.
@hadley
Copy link
Member

hadley commented Mar 19, 2012

Thanks Brian - will pull next time I'm working on ggplot2.

@wch
Copy link
Member

wch commented Mar 27, 2012

@BrianDiggs Could you add an entry in NEWS?

BrianDiggs added a commit to BrianDiggs/ggplot2 that referenced this pull request Apr 5, 2012
Address Issue tidyverse#448 request for news entry related to push request.
@BrianDiggs
Copy link
Contributor Author

It was easier to create another pull request with the update to NEWS (#469) because when I branched off to make the fix, NEWS didn't have anyplace to put new entries and I wanted each to apply cleanly. And I can't rebase an already public branch.

@wch
Copy link
Member

wch commented Apr 5, 2012

For future reference, rebasing public branches actually isn't as bad as commonly believed. I think it'll only cause problems if someone else fetches your branch and starts working off of it. I frequently rebase my pull requests... there was a small discussion about it in #374.

wch pushed a commit that referenced this pull request Apr 5, 2012
Address Issue #448 request for news entry related to push request.
@wch
Copy link
Member

wch commented Apr 5, 2012

The commits have been rebased onto master.

@wch wch closed this Apr 5, 2012
kohske pushed a commit to kohske/ggplot2 that referenced this pull request Apr 27, 2012
Address Issue tidyverse#448 request for news entry related to push request.
@lock
Copy link

lock bot commented Jan 19, 2019

This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/

@lock lock bot locked and limited conversation to collaborators Jan 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants