[META: Ideas for near future]

[dmpe]

This is meta issue (for myself; label would be nice however)

• conform to style : http://adv-r.had.co.nz/Style.html / Google R
• replace 2015-07-10 11:18:47.945 getResponse: Error in httr GET: 401 http://data.cityofchicago.org/resource/j8vp-2qpg.json
  with a nice message/warning/stop functions Move from RUnit to testthat #48, Split functions and other smaller improvements for 1.6.3 #53
• close all issues which need to be closed
• Add support for geojson downloads #43

See also
https://github.com/Chicago/RSocrata/wiki/Roadmap#planned-releases

[dmpe]

@geneorama
How does it look with the sprint7 branch ? So many good changes but somehow abandoned, fixing bugs such as #19.

Before one tackles e.g. #43 I think it would be good to incorporate many of them, e.g. splitting RSocrata.R in at least 3 R files or making it more according to style guide (google + hadley etc.)

[tomschenkjr]

@dmpe-

• Yeah. We're going to modify it a bit since we have some ways we approach things (e.g., package::function).
• Absolutely, we need some better error handling for HTTP issues instead of relying on httr's returns. Will help with the unit testing issues Issue Add specific error message for non-SoDA resource #16 is similar and is need
• On closing issues, they're often closed when we finally push to master since "closing" is included in the commit message.
• @geneorama changes--as a whole--were pretty big and are aiming to be incorporated in the v2 of the package. I see some new functions or at least the structure of functions needing to change because of the new API functionality (e.g., Add support for geojson downloads #43).

We may want to make some of these changes in minor and bug releases. For instance, 1.6.2 to split R files and better error handling. Then #43 can be slated for v1.7 or 2.0 depending if we get this all done at once. However, I think we need to change the function syntax a bit (see sprint7 branch) to accomidate some of Socrata's new API functionality.

I've updated the roadmap to reflect some of these desires in version 2.0.