… and fixed a spec issue with the new controller.url not automatically casting models into their respective IDs.
…_options_from_args! but this may be resolved with the next push of changes to the 0.9.8 Router changes.
…e URL generation specs fail still.
…n/json but will fail to anything. [#62 state:resolved]
…ler) so the test can legitimately fail. Made the dispatcher search full constant strings (like Foo::Bar) using the Extlib functionality. [#63 state:resolved]
…yon::Client support having the Content-TType specified for the client and formatting the body appropriately. Also expanded specs. [#61 state:resolved]
…application/json. Added specs for both the PostBodyContentTypeParser and the JSONP Rack middleware.
…failing. [#60 state:resolved]
…3.0 until I can figure out why it breaks things.
…ataObject's core_ext to form the 'extlib' project
…parsed due to not being escaped. Includes new tests and additional testing actions for generated apps (for testing the client). [#57 state:resolved]
…(to prevent Capified Halcyon apps from loading config/deploy.rb and dying).
…ooks twice, for instance).
… of data.
… to allow indifferent access (since YAML and JSON won't know a difference between strings and symbols).
…not being specified as symbols. [#55 state:resolved]
…m by default (making application configuration by default Ruby and not YAML). However, YAML still works. [#54 state:resolved]