-
Notifications
You must be signed in to change notification settings - Fork 422
vue: add jest testing hints on imports #2568
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+29
−0
Merged
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -289,6 +289,27 @@ const myComponent = defineComponent({ | |
| The injected `jsonforms` object is not meant to be modified directly. | ||
| Instead it should be modified via the provided `dispatch` and by changing the props of the `json-forms` component. | ||
|
|
||
| ### Testing with Jest / Vitest | ||
|
|
||
| When testing custom renderers with Jest or Vitest using CJS transforms, `vue` must be imported **before** `@jsonforms/vue` in your renderer files. | ||
| This is due to the CJS bundle eagerly evaluating Vue component definitions at `require()` time, which can cause issues when Jest's module resolution processes imports sequentially. | ||
|
|
||
| ```ts | ||
| // Correct - import vue before @jsonforms/vue | ||
| import { defineComponent } from 'vue'; | ||
| import { rendererProps, useJsonFormsControl } from '@jsonforms/vue'; | ||
| ``` | ||
|
|
||
| ```ts | ||
| // May cause errors in tests: | ||
| // "Property 'controlWrapper' was accessed during render but is not defined on instance" | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The quoted error references |
||
| import { rendererProps, useJsonFormsControl } from '@jsonforms/vue'; | ||
| import { defineComponent } from 'vue'; | ||
| ``` | ||
|
|
||
| This only affects test environments using CJS module transforms. | ||
| Browser builds using Webpack, Vite, or other ESM-aware bundlers are not affected. | ||
|
|
||
| ## License | ||
|
|
||
| The JSON Forms project is licensed under the MIT License. See the [LICENSE file](https://github.com/eclipsesource/jsonforms/blob/master/LICENSE) for more information. | ||
|
|
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit generic. The cause seems to be that we call
defineComponentat module load sovueneeds to be initialized first. Do other component libraries have the same issue?