feat(functions): add low-level functions.fetch API #435
netanelgiladAnnotations
3 errors and 1 warning
|
test
Process completed with exit code 1.
|
|
tests/unit/functions.test.ts > Functions Module > should not fallback to app-scoped functions endpoint on 404:
tests/unit/functions.test.ts#L490
AssertionError: expected 'https://api.base44.com/api/api/functi…' to be 'https://api.base44.com/api/functions/…' // Object.is equality
- Expected
+ Received
- https://api.base44.com/api/functions/streaming_demo/deep/path
+ https://api.base44.com/api/api/functions/streaming_demo/deep/path
❯ tests/unit/functions.test.ts:490:40
|
|
tests/unit/functions.test.ts > Functions Module > should fetch function endpoint directly for streaming:
tests/unit/functions.test.ts#L471
AssertionError: expected "spy" to be called with arguments: [ …(2) ]
Received:
1st spy call:
Array [
- "https://api.base44.com/api/functions/streaming_demo",
- Any<Object>,
+ "https://api.base44.com/api/api/functions/streaming_demo",
+ Object {
+ "body": "{\"mode\":\"sse\"}",
+ "headers": Headers {},
+ "method": "POST",
+ },
]
Number of calls: 1
❯ tests/unit/functions.test.ts:471:23
|
|
test
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. 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/
|