Use item_lookup_field for DELETE methods

Existing code uses lookup to recover document. Once we've found the
"original" document we don't need lookup anymore and we can use
"original" document ID_FIELD.
Using lookup[ID_FIELD] forces to use just the ID_FIELD on path.

This change would be consistent with GET and PATCH methods where
changing item_lookup_field let items to be recovered/updated with other
fields than _id (or ID_FIELD for global configuration)
Xavi Cubillas
Merge branch 'xcubillas-develop' into develop
Merge branch 'develop' for v0.1.1 release
v0.1.1 release date
Extracted new method for registering resource on the fly.

Refactored Eve's configuration handling and created Eve.register_resource()
method. If there exists given resource in the config, its settings is
overwritten by calling this method.

This may be base method for all ODM/ORM adapters which create schema out of
model and need to add it into Eve's config. #126
Added tests for Eve.register_resource().

#126.
Fixes in identitation to make Travis happy.
Bump version to 0.2-dev.
typo mistake

I think there is a typo mistake here. although a 'friends' field in 'author' doesn't seems to fit.

also, there was missing the 'embedded=' at the url
Read-only field with default value would trigger validation error.
Sphinx attributes for #160.
New method Eve.register_resource().
Stanislav Heller
flake8 fix
Allow use of dict object as custom settings.

Partially addresses #146, with test and documentation update.
Allow JSON encoding at the DataLayer level.

JSON encoding is now handled at the DataLayer level allowing for specialized,
granular, data-aware encoding. Also, since the JSON encoder is now a class
attribute, extensions can replace the pre-defined data layer encoder with their
own implementation. Closes #102.