Bugfix - correct 'plotly-related' yPlot()
jitter issue
#11
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.
Re-make of #9 since I built my own fix before seeing that version.
Per investigation by @j-andrews7, discovering the root cause of this long-standing dittoSeq-issue, adds a column to the data_frame when needed (
group.by
andcolor.by
not the same) and uses that column orgroup.by
for explicitly setting thegroup
aesthetic for the jitter geom.This PR also turns showing hover.data back on for yPlot
I had commented the code for utilizing this data out because of the bug addressed here!
ToDo
hover.round.digits
to control length of numeric values displayedgroup.by
/sample.by
/color.by
to the data shown forbarPlot()
andfreqPlot()
scatterPlot()
hover.data