update readme and package.json
Merge pull request #81 from stormpath/release-0.5.0

Release 0.5.0
fix: getAccount error causes undefined object error

previously we would try to read account, which is undefined if
there is an error
Merge pull request #86 from stormpath/fix-error

fix: getAccount error causes undefined object error
update readme and package.json
Merge pull request #87 from stormpath/release-0.5.1

Release 0.5.1
remove requirement that api auth requests be GET or POST

this is not necessary though we do still require that oauth exchange
requests use POST, per the spec
cleanup

oops
Merge pull request #90 from stormpath/fix-apiauth-methods

remove requirement that api auth requests be GET or POST
update readme and package.json
Merge pull request #91 from stormpath/release-0.5.2

Release 0.5.2

Fixes #89
updated docs for application.getAccount()

* better document the object literal as providerOptions
* reduced usage to one example
* linked to product guide for social providers
* defined the result object as providerAccountResult
Merge pull request #92 from stormpath/docs

updated docs for application.getAccount()
it tests for custom data on all supported resources
more it tests

oh so many more to write..
tenant can have custom data, too
getCustomData vs resource.customData

getCustomData is used when you did not expand the
custom data on the parent resource

if you did expand custom data on the parent resource,
then you can use it directly from resource.customData

these tests, docs and Tenant resource change are
in reflection of that
implement application.getCustomData()
getCustomData for directory, and fix expansion issue

I observed #85 while writing the it tests for custom data
on directories, thus I’m fixing it in this commit.

The fix is to bring back the logic of “don’t cache
any requests that have query options”.  I had previously
removed this but now I’m bringing it back, as it’s simpler
than trying to write fancy query caching rules into the
datastore.

You can achieve cache warming by expanding the resource
the first time you get it, then using the getter methods
on subsequent request for the same data.
update docs