(fix) Workaround for duplicate decorators in def -> async def #65
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.
Related to: #55
Observation:
- When Asyncifing a decorated function, the decorators are duplicated
Understanding:
- In
apply()
method of_ReplaceCodeSegmentAction
, thelines
exclude the decorators (fromposition_for()
)- Building the
replacement
is based on thecontext
, which includes the decorators- Replacing the
lines
slice with thereplacement
ends up duplicating the decoratorsProposal:
- A possible solution is to include the decorators in the
lines
since_resyntesize()
works with thecontext that includes the decorators