Feature: virtual decorator #1350
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
1 task
|
Can you add tests? |
LotfiMEZIANI
force-pushed
the
feature/virtual-decorator
branch
2 times, most recently
from
75989b8
to
96410d4
Compare
It's done. But i don't know if I done it in the correct folder ( |
LotfiMEZIANI
force-pushed
the
feature/virtual-decorator
branch
from
96410d4
to
7f4df5b
Compare
|
Would love to see this get merged. |
|
Any updates here? |
|
@kamilmysliwiec, waiting for the merge, if everything is ok. |
|
@LotfiMEZIANI @kamilmysliwiec Any news on this? this should have merged by now... |
|
@KevinEdry, for me it’s fine, I’m waiting for the validation of an owner of the repository (ping @kamilmysliwiec ) |
|
bump I just happen to need this. |
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #1349
What is the new behavior?
Described here : #1349
Does this PR introduce a breaking change?