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
IT tests for resource.customData.get()
updated docs for custom data

attempt to make the usage clearer, because it’s a bit
different if you don’t expand custom data when you request
the parent resource
typo
Merge pull request #96 from stormpath/custom-data

Custom data for all supported resources