fix: respect useDefineForClassFields=false setting #156
Conversation
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
|
|
orgads
changed the title
6 tasks
|
@hannoeru ping |
hannoeru
reviewed
Apr 16, 2025
This setting defaults to true, so if not explicitly set to false, it is not propagated to the transformer. See vitest-dev/vitest#7805
orgads
force-pushed
the
use-define-false
branch
from
44e2a38 to
463978d
Compare
|
@hannoeru Anything else? |
|
Thank you. |
|
🎉 This PR is included in version 1.5.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
This setting defaults to true, so if not explicitly set to false, it is not propagated to the transformer.
Linked Issues
vitest-dev/vitest#7805