Deriving ElasticType Implements DocumentType

[KodrAus]

It's a bit weird that deriving ElasticType implements a trait called DocumentType (it might also add a mapping type and derive traits for that).

This should be aligned with the trait bound you'd use to accept a document type.

The options are:

Rename DocumentType to ElasticType:

#[derive(ElasticType)]
struct MyData {
    id: i32,
    title: String
}

fn with_doc<TDocument: ElasticType>(doc: TDocument) {

}

Rename ElasticType to DocumentType:

#[derive(DocumentType)]
struct MyData {
    id: i32,
    title: String
}

fn with_doc<TDocument: DocumentType>(doc: TDocument) {

}

Rename both to ElasticDocument:

#[derive(ElasticDocument)]
struct MyData {
    id: i32,
    title: String
}

fn with_doc<TDocument: ElasticDocument>(doc: TDocument) {

}

I don't have a strong leaning yet. I'll play with it in some actual code and see which one works out best.

[KodrAus]

The same goes for deriving ElasticDateFormat.

I'll do an experiment and see what happens if you have conflicting derives.