Refactor contexts to context #945
Merged
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
inancgumus
approved these changes
Jun 20, 2023
Yeah, that's the next task 😅 |
Now that we can only store a single browserContext per browser, the contexts API doesn't make sense to return more than one browserContext so instead we've refactored it to return the only browserContext or nil.
ankur22
force-pushed
the
refactor/925-refactor-contexts
branch
from
4bf5d81
to
440aaab
Compare
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.
Description of changes
Now that we can only store a single browserContext per browser, the contexts API doesn't make sense to return more than one browserContext so instead we've refactored it to return the only browserContext or nil.
Checklist