-
Notifications
You must be signed in to change notification settings - Fork 626
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
Carson scales free #167
Carson scales free #167
Conversation
You might find this script I wrote helpful for comparing the output of Installing from GitHub is perhaps inefficient, but it might be worth avoiding nasty |
Ah, crud. I messed with the white space a bit which makes the last commit diff hard to read. You can add |
@cpsievert Regarding whitespaces, I go for RStudio's indentation. In this respect, it looks like some of your whitespace changes are 'fixes', so that's all good. I'm not sure about others (see inline comments). |
shape=function(pch) { | ||
pch2symbol[as.character(pch)] | ||
}, | ||
direction=identity) |
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.
Why this change? Please keep it the way RStudio does indentation.
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.
Hmm, no good reason. I'll change that back
Sweet. That's what I prefer to. I also prefer f <- function() {
print("hi")
} over f <- function()
{
print("hi")
} so I'd be happy to change that as well |
Nice! hey @tdhock is it possible/easy to run that test table on this branch? |
I'm pretty sure Toby's current implementation would only support visual testing of one branch at a time. Perhaps we could do something similar in a "username.github.com" repo with a folder for each branch? |
yes it should be possible to run the test table on this branch, but I will need to do a little hacking. Will post a link to the updated table when I get a chance to work on it. |
check out the test table there are some cases with weird disappearing boxes (not your fault, this test only exists on the toby-fixes branch) https://github.com/ropensci/plotly/blob/toby-fixes/tests/testthat/test-ggplot-ticks.R#L51 |
Sweet, thanks @tdhock! Will toby-fixes be merged into master soonish? Or maybe we should merge carson-scales-free and toby-fixes? |
Cool - @tdhock @mkcor - should we move these *.r files that have the cookbook examples branch (https://github.com/ropensci/plotly/tree/add-r-cookbook-tests/tests/cookbook-test-suite) into the testhat directory (or elsewhere) in master so that the test-table can pick up on that rich set of examples? |
@cpsievert I don't know how long it will be before toby-fixes it merged into master, so I would suggest to pull changes from toby-fixes into your branch. @chriddyp @mkcor I agree that it is a good idea to add examples from the cookbook branch to the test table. In my opinion the easiest way to do this would be to just add them as tests/testthat/test-*.R files under toby-fixes. I can do that if you guys tell me which of https://github.com/ropensci/plotly/tree/add-r-cookbook-tests/tests/cookbook-test-suite you would like to include... or would you like to include all of the *.r and *.R files? |
@tdhock OK, that sounds good. All of them are good except |
@cpsievert [On curly braces] Absolutely. It's not only a preference, it's our style guide (https://github.com/ropensci/plotly/wiki/Development-guidelines#coding-style, https://google-styleguide.googlecode.com/svn/trunk/Rguide.xml#curlybraces). |
@cpsievert @tdhock |
@cpsievert @tdhock For reference, https://github.com/ropensci/plotly/wiki/Development-guidelines#a-few-guidelines -- Thanks @chriddyp for updating and cleaning that up! |
@cpsievert Can you please revert c542520 ? You shouldn't find yourself merging another feature/dev/wip branch into your own feature branch. Merging |
@mkcor ok, I removed that merge from the history on this branch |
@cpsievert Amazing! Just pulled your branch for a quick final review. |
@@ -168,6 +170,9 @@ gg2list <- function(p){ | |||
gglayout <- built$panel$layout | |||
## invert rows so that plotly and ggplot2 show panels in the same order | |||
gglayout$plotly.row <- max(gglayout$ROW) - gglayout$ROW + 1 | |||
## ugh, ggplot counts panel right-to-left & top-to-bottom | |||
## plotly count them right-to-left & *bottom-to-top* |
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.
Please use a single #
for comments (see https://github.com/ropensci/plotly/wiki/Development-guidelines#coding-style and https://google-styleguide.googlecode.com/svn/trunk/Rguide.xml#comments).
just re-made the test table on your branch I noticed a couple of regressions, can you please check them out? |
by the way do you want to get added to ropensci so you can add a branch under the main plotly repos for your next branch/PR? i guess it doesn't really matter but I figured I would ask. |
Thanks @tdhock. I'll hopefully have a fix soon. It'd be nice to be added, but not essential. |
Hey @cpsievert - how is this going? anything I can do to help get this through? A few users wrote in about scales-free this weekend! |
I just updated the test table (note that it didn't update automatically because this PR was initiated from my fork). http://ropensci.github.io/plotly-test-table/ I don't see any problems, and I'd be OK with merging now, but we can certainly add more of the cookbook tests if you'd like. |
Fantastic, the visual tests look good! 👍 from me |
Cool, thanks. Should I wait for a +1 from @mkcor? |
OK, I actually just noticed a regression in facet strip labels. I'll fix later today and let everyone know when it's ready. |
@tdhock it appears your latest push to plotly-test-table somehow overwrote homepage links to commits I made earlier today -- http://ropensci.github.io/plotly-test-table/ You can still see them here though -- http://ropensci.github.io/plotly-test-table/tables/f800c1249fc36072c1b4dd775b88659144b80f17/ |
The homepage links are generated via the files in tables/* so I think the links will show up the next time the table is re-made. |
@tdhock @chriddyp please have a look at the table and +1 (it looks good to me and I'm ready to merge) http://ropensci.github.io/plotly-test-table/tables/f9e252af61276fd40168fc8916024877c7f2f6a3/ There was a failure in downloading contours (this seems to be quite common when I However, this test for the previous commit looks good (the only is difference is NEWS/DESCRIPTION) |
are you sure it is a download error? If so there should be a log file... if there is not a log file then there is a bug in the plotly-test-table code. |
If it is a download error you get a log line via this code https://github.com/ropensci/plotly-test-table/blob/gh-pages/table.R#L248-L250 but you are seeing an error due to this code https://github.com/ropensci/plotly-test-table/blob/gh-pages/table.R#L265-L270 the only reason why I can think that would be happening is that the py$ggplotly function returns an error that is the code for SENDING the plotly, not for downloading it. I guess I may need to add some code to attempt retries for the sending step as well. |
OK, good to know, it's probably because I'm on a crappy wifi connection On Tue, Mar 10, 2015 at 2:42 PM, Toby Dylan Hocking <
|
I made the table again (after merging with master which now has the fix for ribbon transparency) and everything looks good (with no caveats :) |
+1 |
Howdy @chriddyp @mkcor @tdhock!
The purpose of this pull request is to fully implement
facet_wrap(..., scales = 'free')
.It also seems possible to implement space = "free", but perhaps that should be in a separate pull request.