Refactor decorators class structure

[felipesabino]

• Refactor decorators to use new folder structure

- decorator
- metadata-builder
- metadata
  - args
  - types
  - options
- type-factory
- specs

• Avoid using Reflect.defineMetadata and Reflect.getMetadata all over the code base to improve readability. Use specific MetadataArgsStorage methods instead.

• Deprecate support decorators due to improvement from Decorators less verbose and subscriptions #14

  • @Pagination
  • @Description
  • @List
  • @NonNull
  • @UseContainer - Remove decorator and add it as a function like useContainer from pleerock/routing-controller

• Decorators

  • @UnionType
  • @EnumType + @Value
  • @Field + @Arg + @OrderBy + @Root + @Before + @Ctx
  • @ObjectType
  • @InputObjectType
  • @Query
  • @Mutation
  • @Subscription
  • @Schema

[thiago-soliveira]

Just some info about the @UseContainer() decorator. Its role is to tell the graphql decorator to use the passed container for classes instatiation, just so the typedi injection works on classes decorated with ObjectType or InputObjectType.
So... It was implemented as a decorator, but it actually should be a function that would get called on app configuration. Just like useContiner from pleerock/routing-controller

[felipesabino]

So... It was implemented as a decorator, but it actually should be a function that would get called on app configuration

Oh sure! I completely missed that on #32 (https://github.com/indigotech/graphql-schema-decorator/pull/32/files#diff-b4975713b292137c31ec2d18544e2323). I updated the issue description to reflect your comment, thanks! 👍