wip: fake roc v2 api

[stropitek]

@targos this is really a draft right now

I'm trying to have something more OO than the previous implementation. I'm trying to have an abstract class that the fake and real apis will extend. I'm not sure if it would be better to use inheritance (extends) or polymorphism (implements). I went for inheritance but I think polymorphism might actually have more sense because the implementations are very different and don't share much with a base class.

The basic idea is to have a Roc class that handles basic requests like getUser, and methods that return more complex objects, for example getDocument which provides methods and handles state for a single document. We could have another method getQuery which handles queries to roc.

[targos]

All of this is very abstract for now. Are you asking if you should continue in this direction?
It doesn't seem bad but it's difficult to review without knowing what part of this is WIP and what is "ready".
For example, I find weird that getUser is in the abstract class but not getDocument and create.

[targos]

I'd prefer an option to fetch: document.fetch({ force: true })

[stropitek]

I think I'm not going to put a lot of state in Document class. Except for the synchronization feature (polling the document to know if it's still up to date). I feel like having:

document.addAttachment(...);
document.removeAttachment(...);
document.save();

would be a duplication of state since we would also need to have this state in redux. I'm going more for:

document.update(newContent, newAttachments, deletedAttachments);

so that document class remains almost stateless.