nmerge three exmaples into one

Author: capaj

README.md

@@ -174,13 +174,15 @@ class Product {
 
 ## Compared to type-graphql
 
-There is a much more popular [library](https://github.com/19majkel94/type-graphql) with the same goals-so what makes decapi different? Decapi has smaller API surface-it only has hooks on top of the basic decorators for constructing schemas.
-Whereas type-graphql has authorization, middleware, guards.
-Also decapi supports graphql v16. Typegraphql is still only supporting Graphql v15
+There is a much more popular [library](https://github.com/19majkel94/type-graphql) with the same goals-so what makes decapi different?
+
+1.  decapi does reflection through typescript-rtti, so it can infer 99% directly from typescript types without having to write them twice
+2.  Decapi has smaller API surface-it only has hooks on top of the basic decorators for constructing schemas. Whereas type-graphql has authorization, middleware, guards.
+3.  Also decapi supports graphql v16. Typegraphql is still only supporting Graphql v15
 
 ## Why forking?
 
-I wanted to contribute to [typegql](https://github.com/prismake/typegql) and work on it together with @pie6k, but it soon became obvious that we both have something different in mind. Just to briefly summarise the differences:
+Initially I wanted to contribute to [typegql](https://github.com/prismake/typegql) and work on it together with @pie6k, but it soon became obvious that we both have something different in mind. Just to briefly summarize the differences:
 
 - decapi has `@DuplexObjectType` and `@DuplexField`
 - decapi supports interfaces and mixins
@@ -189,9 +191,10 @@ I wanted to contribute to [typegql](https://github.com/prismake/typegql) and wor
 - InputObjectType argument passed to Field/Query method is not just a plain object, but an instance of it's class.
 - decapi allows you to have an empty object type-you can populate it with fields at runtime
 
-## Before `1.0.0`
+## Upgrading from 1.0.0 to 2.0.0
 
-Before version `1.0.0` consider APIs of `decapi` to be subject to change. We encourage you to try this library out and provide us feedback so we can polish it to be as usable and efficent as possible.
+This major was a complete rewrite of the reflection of types. From 2.0.0 decapi uses typescript-rtti to infer graphql types from typescript. This works for 99% of TS types.
+This means you should always have your decorators without explicit `type` property.
 
 ## TC39 decorators proposal
 

examples/basic-express-server/package-lock.json

@@ -6,7 +6,7 @@
   "dependencies": {
     "apollo-server-core": "^3.6.7",
     "apollo-server-express": "^3.6.7",
-    "decapi": "^2.0.0-beta.1",
+    "decapi": "^2.0.0-beta.2",
     "express": "^4.17.3",
     "graphql": "^16.3.0",
     "ts-node": "^10.7.0",

examples/basic-express-server/package.json

@@ -1,4 +1,5 @@
 import { SchemaRoot, Query, compileSchema } from 'decapi'
+import { MySchemaCustomDecorators } from './schemaWithCustomDecorators'
 
 @SchemaRoot()
 class MySchema {
@@ -8,4 +9,4 @@ class MySchema {
   }
 }
 
-export const schema = compileSchema(MySchema)
+export const schema = compileSchema([MySchema, MySchemaCustomDecorators])

examples/basic-express-server/schema.ts

@@ -23,7 +23,7 @@ class CustomObject {
 }
 
 @SchemaRoot()
-class MySchema {
+export class MySchemaCustomDecorators {
   @Query()
   getCustomObject(stringValue: string): CustomObject {
     const object = new CustomObject()
@@ -32,4 +32,6 @@ class MySchema {
   }
 }
 
-export const schema = compileSchema(MySchema)
+export const schemaWithCustomDecorators = compileSchema(
+  MySchemaCustomDecorators
+)