-
Notifications
You must be signed in to change notification settings - Fork 74
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
test: Add e2e test for lambda data client #2228
base: stocaaro/client-schema/main
Are you sure you want to change the base?
test: Add e2e test for lambda data client #2228
Conversation
|
import { Amplify } from 'aws-amplify'; | ||
import { generateClient } from 'aws-amplify/data'; | ||
import type { Schema } from '../../data/resource.js'; | ||
// @ts-ignore |
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.
Esbuild during synth is fine with all of this, but the ts check before synth is unhappy. It looks like a workaround was used for data-storage-auth-with-triggers-ts
of setting up fake files to make the pre-synth check happy. Should I replicate that here? It would avoid the exclude change in the tsconfig below too.
Seems fine, but also very fake since this file isn't being built in the project.
…nto stocaaro/client-schema/e2e-test
This change has been merged into #2224 |
Problem
The lambda data client needs to be covered by an e2e test.
Changes
Validation
Tested using
npm run test:dir packages/integration-tests/lib/test-e2e/sandbox/data_and_function_project.sandbox.test.js
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.