fix #2108 Options provide should allow symbol keys - #2109
Open
DesselBane wants to merge 1 commit into
Open
Conversation
✅ Deploy Preview for vue-test-utils-v1 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
DesselBane
force-pushed
the
fix/provide-should-allow-symbol-keys
branch
from
October 20, 2025 09:32
16b4ec4 to
46512b4
Compare
DesselBane
marked this pull request as ready for review
October 20, 2025 09:37
DesselBane
marked this pull request as draft
October 22, 2025 05:43
DesselBane
marked this pull request as ready for review
October 22, 2025 05:43
DesselBane
force-pushed
the
fix/provide-should-allow-symbol-keys
branch
from
October 22, 2025 09:29
46512b4 to
0563d1e
Compare
This file contains hidden or 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
1 participant
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.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch.fix #xxx[,#xxx], where "xxx" is the issue number)Other information:
Fixes #2108