Decorators/single #4
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Saw your video about Higher Order Resolvers and your question about dynamic decorators. I grabbed the opportunity to try it and learn more about decorators.
This code is to exemplify the passing of a single dynamic decorator.
About the abstract doubt in the last part of the video. I haven't tried it, but i don't think that you can instantiate an abstract class, so your code should be correct as it is.
I will send another PR for the array of decorators situation. I could have put everything in a single PR. But in my explorations, i separated the features in different branches as i got them to not mangle them.
Edit: disregard the earlier closing of the PR. It is late here :(