[refactor!]: changed resultObservable deep -> ref globally #166
js2meAnnotations
4 errors and 1 warning
|
build-and-test (24)
Process completed with exit code 1.
|
|
src/query.test.ts > Query > onError should keep listener args original and transform result.error:
src/query.test.ts#L4584
AssertionError: expected 1st "vi.fn()" call to have been called with [ ObjectContaining{…}, undefined ]
- Expected
+ Received
[
- ObjectContaining {
- "message": "boom-1",
+ Error {
+ "message": "transformed:boom-1",
},
undefined,
]
❯ src/query.test.ts:4584:23
|
|
src/query.test.ts > Query > "setData" method > computed.structs should be reactive after update query data using mutation:
src/query.test.ts#L1498
AssertionError: expected "vi.fn()" to be called 2 times, but got 1 times
❯ src/query.test.ts:1498:30
|
|
src/query.test.ts > Query > "setData" method > should calls reactions after update query data using mutation:
src/query.test.ts#L1313
AssertionError: expected "vi.fn()" to be called 2 times, but got 1 times
❯ src/query.test.ts:1313:27
|
|
build-and-test (24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|