Add typings to package.

[mathieutu]

Hi,
Here are some typescript typing to resolve #7.
This is my first typings, and I'm a total noob in TS, so it's totally opened for expertise, to learn.

The only thing I can say is, like it's done, it works! 😅
I'm using TS on my project, and it correctly recognize all the types.

Thanks for your work on this package!

[coveralls]

Pull Request Test Coverage Report for Build 53

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 35:	0.0%
Covered Lines:	221
Relevant Lines:	221

---

💛 - Coveralls

[b1f6c1c4]

@b4dnewz @Xilesun Could you two help review this PR?

[Xilesun]

@b1f6c1c4 It seems work well in my project.
@mathieutu Good job!

I think you can make a PR on DefinitelyTyped, so that we can use it conveniently by npm install @types/graphql-advanced-projection later. 👍

[mathieutu]

@Xilesun why sould we push that on @types if @b1f6c1c4 is ok to merge? DefinitelyTyped is just for repos which don't have typings in them.

Quoting:

When a package bundles its own types, types should be removed from DefinitelyTyped to avoid confusion.

[Xilesun]

@mathieutu Your opinion is right.

[b1f6c1c4]

genResolvers does NOT give GraphQLFieldResolver<,>.
It produces:

{
  User: {
    userId: (parent, args, context, info) => parent._id,
    field1: (parent, args, context, info) => parent.mongoA,
  },
}

while GraphQLFieldResolver<,> is essentially the type of (parent, args, context, info) => any.

[mathieutu]

Indeed, I've missed a level.

[b1f6c1c4]

@mathieutu Would you please use a linter (such as tslint) to lint the code, enforcing a consistant coding style? I found that there are inconsistent spaces and semicolons.