Feature/delete and some post

[ebsaral]

What I did?

• Created the "delete" delegate for the client after creating Destroyer
• Enhanced Poster to return an object instead of a simple response. I am not sure if it should be backward compatible but I implemented in this way.
• Added a new data model in poster for event creation.
• Added spec (more tests needed to validate event creation and deleting feature even though I tested it many times on local). I can add them later.
• Updated ReadMe.
• Drank lots of coffee (irrelevant data) lol.

[coveralls]

Coverage increased (+0.6%) when pulling 3bd0975 on eminbugrasaral:feature/delete-post into 07b0309 on neektza:master.

[coveralls]

Coverage increased (+0.96%) when pulling 361b55b on eminbugrasaral:feature/delete-post into 07b0309 on neektza:master.

[coveralls]

Coverage increased (+0.96%) when pulling 4e65b40 on eminbugrasaral:feature/delete-post into 07b0309 on neektza:master.

[coveralls]

Coverage increased (+0.96%) when pulling 361b55b on eminbugrasaral:feature/delete-post into 07b0309 on neektza:master.

[coveralls]

Coverage increased (+0.96%) when pulling 361b55b on eminbugrasaral:feature/delete-post into 07b0309 on neektza:master.

[neektza]

One nitpick ...

What is the intention behind client.post(:event, { ... new_event_data ... }) returning an Event object instead of just returning a plain hash?

[neektza]

Nevermind, I'll merge this anyway because the library will be going in this way anyway. Every response will be an object because it'll enable us the build more fluent APIs.

[neektza]

Merged by 3871205