Skip to content
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

Remove deprecated messages field from event #2106

Merged
merged 1 commit into from
Oct 11, 2024
Merged

Conversation

sobolk
Copy link
Member

@sobolk sobolk commented Oct 11, 2024

Problem

event.messages is deprecate and ready for removal after data construct shipped.

Changes

  1. Remove deprecated field
  2. Adjust logic and tests.

Validation

Existing tests.

Checklist

  • If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
  • If this PR requires a change to the Project Architecture README, I have included that update in this PR.
  • If this PR requires a docs update, I have linked to that docs PR above.
  • If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@sobolk sobolk added the run-e2e Label that will include e2e tests in PR checks workflow label Oct 11, 2024
Copy link

changeset-bot bot commented Oct 11, 2024

🦋 Changeset detected

Latest commit: 3b1a025

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@aws-amplify/ai-constructs Minor
@aws-amplify/backend-ai Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@@ -51,6 +49,28 @@ type ConversationTurnAppSyncResponse = {
content: string;
};

type ConversationMessage = {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

had to duplicate these for test purposes since we're hiding them in ai-constructs.

@sobolk sobolk marked this pull request as ready for review October 11, 2024 16:49
@sobolk sobolk requested review from a team as code owners October 11, 2024 16:49
@sobolk sobolk merged commit 46a0e85 into main Oct 11, 2024
57 of 58 checks passed
@sobolk sobolk deleted the remove-messages-field branch October 11, 2024 19:53
vigy02 added a commit that referenced this pull request Oct 31, 2024
…nstruct (#2087)

* fix: clearing the .amplify/generated/env/ before synthesis

* fix: clearing the .amplify/generated/env/ before synthesis

* fix: clearing the .amplify/generated/env/ before synthesis

* fix: clearing the .amplify/generated/env/ before synthesis

* fix: clearing the .amplify/generated/env/ before synthesis

* fix: clearing the .amplify/generated/env/ before synthesis

* chore: add changeset

* fix: clearing the .amplify/generated/env/ before synthesis

* fix: clearing the .amplify/generated/env/ before synthesis

* fix: clearing the .amplify/generated/env/ before synthesis

* fix: Clear generated env directory before shim generation

* fix: Clear generated env directory before shim generation

* fix: Clear generated env directory before shim generation

* fix: Clear generated env directory before shim generation

* chore: add changeset

* fix: Clear generated env directory before shim generation

* fix: Clear generated env directory before shim generation

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* feat: adding custom lambda function trigger for email

* cleanup

* chore: removed unwanted changesets

* chore: preparing for merge

* chore: preparing for merge

* chore: preparing for merge

* feat: added a functionality to translate auth-props for custom fucntion email

* chore: added changeset

* chore: added new API

* feat: added a functionality to translate auth-props for custom fucntion email

* feat: added a test case to cover custom function in backend-auth

* feat: added a test case to cover custom function in backend-auth

* feat: added a test case to cover custom function in backend-auth

* feat: added a test case to cover custom function in backend-auth

* feat: added a test case to cover custom function in backend-auth

* feat: narrowed down the permission by updating the conditions

* Refactored the code

* Refactored the code

* added a test case for checking lambdaTrigger={} empty condition

* added a test case for checking lambdaTrigger={} empty condition

* Merge Branch

* Merge Branch

* Merge Branch

* Merge Branch

* Merge Branch

* Merge Branch

* Merge Branch

* Merge Branch

* Merge Branch

* Merge Branch

* fixed the code to use addTrigger instead of manually setting up permissions

* added KMS Key for customEmailSender

* changed KMS key to not read-only

* changed the test case to include lambdaArn

* add a test case validation for KMS key

* fixed the code to use addTrigger instead of manually setting up permissions

* added KMS Key for customEmailSender

* changed KMS key to not read-only

* changed the test case to include lambdaArn

* add a test case validation for KMS key

* detect transform errors with multiple errors (#2102)

* detect transform errors with multiple errors

* new method of getting multiple transform errors

* Add minify option to defineFunction (#2093)

* Add minify option to defineFunction

* Add unit tests and e2e tests when set minify option to false

* Add changeset

* Update API.md

* add bundling options

* Update .changeset/pink-rockets-dance.md

* use optional chaining

* include funcNoMinify into function.ts

---------

Co-authored-by: Kamil Sobol <[email protected]>

* upgrade constructs (#2103)

* Remove deprecated messages field from event (#2106)

* detect generic CFN stack creation errors (#2108)

* Fix cdk tests when new dependencies are shipped to npm. (#2107)

* Fix cdk tests when new dependencies are shipped to npm.

* try this

* try this

* try this

* try this

* API changes

* Update API changes

* Added kmsKeyArn for custom user KMS keys

* chore: added changesets and updated API's

* chore: added changesets

* Added integration tests for customEmailSender

* updated the API files to reflect master

* feat: added customSenderEmail with types and added exceptions to eslint dict

* chore: Updated API

* chore: Updated API

* chore: updated API

* Delete packages/ai-constructs/API.md

* chore: Updated API

* chore: delete unused file

* chore: update changeset

* chore: update changeset

* chore: Updated API and changeSets

* chore: Updated the API from main

* API updates to resolve conflicting naming

* Updated the types in backend-auth

* chore: Updated changesets

* Added custom Email handler function and refactored the types of auth-construct

* chore: updated API

---------

Co-authored-by: Roshane Pascual <[email protected]>
Co-authored-by: MURAKAMI Masahiko <[email protected]>
Co-authored-by: Kamil Sobol <[email protected]>
Co-authored-by: Kamil Sobol <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
run-e2e Label that will include e2e tests in PR checks workflow
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants