Ryan Nagle
Ryan Nagle
@dryanmedia if you used `self:` instead of `self::` that would cause a fatal error. You'll also need to update any lines referencing `$selection` to use `self::$selection` instead.
I reorganized the tests directory and added test stubs for pretty much everything in ac400c8d6b505aaccd19e2c99ab1be65029a17df. I'm going to punt this ticket to 0.3.1 and address the checklist in @aschweigert's comment...
I think this is related to issue #13. Unfortunately the only workaround I can offer right now is removing commas and dollar signs from the data.
This is now working for the initial sorting of data. However, it looks like there might be a bug in the way Tablesaw handles sorting columns of mixed data types....
Ideally, this knowledge would be stored in one place and used throughout the deploy tools. I'm not sure how to address this. Maybe the IP address can be omitted from...
I agree. In the event that `json.loads` can't parse the response from wp-cli, we should catch the exception (which should be a `ValueError`, I think) and print a friendly error...
OK -- so the word from WPE is that it is not possible to do this programmatically via an API or some such thing, at least for now. If we...
Good point. We can probably address this with a prefix for the rollback tag depending on the environment.