feat: pytest-playwright-asyncio as separate plugin #257
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.
Similar to #184 just as a separate plugin. The main reason for this is that Pylance, the Python language server for VSCode does automatically look for Pytest plugins in order to provide fixture autocompletion. This isn't possible when we dynamically register the plugins, since it just looks at the AST.
If a user wants to partially migrate from sync to async or vice-versa, the user can run Pytest twice, one time with
-p no:playwright
and one time withno:playwright-asyncio
.Pretty-diff between async fixtures and sync fixtures: eb6c55a
Closes #184
Relates #74