-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature - Refactoring more decorators #32
Conversation
@@ -55,6 +59,28 @@ export class MetadataBuilder { | |||
})); | |||
} | |||
|
|||
buildEntrytypeMetadata(target: any, type: EntryType): EntryTypeMetadata[] | undefined { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Entry T ypeMetadata
@@ -0,0 +1,6 @@ | |||
export interface DefaultOption { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
default or common? which one is preferable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what about only Option
, Metadata
and Arg
instead of DefaultOption
, DefaultMetadata
and DefaultArg
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had some progress in other refactoring and will do this in my upcoming refactor PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ Done at ea05219
@Query
,@Mutation
,@Subscription
and@Schema
(now it is missing only@Field
decorator and the ones related)@UseContainer
decorator to decorator folderschema.type-factory
to be less verbose