test(event-handler): coverage 100% for AppSync GraphQL #4261
Conversation
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
boring-cyborg
bot
added
event-handler
2 tasks
svozza
approved these changes
Aug 5, 2025
|
uttam282005
pushed a commit
to uttam282005/powertools-lambda-typescript
that referenced
this pull request
Aug 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Changes
This PR refactors slightly the AppSync GraphQL event handler so that the
aggregateandthrowOnErrorflags have default values at the registry level, rather than when registering the handler - this helps remove code branches and increase test coverage.Additionally, the PR adds missing unit test cases for decorator-based usage of batch query and mutation resolvers.
Finally, the PR consolidates the Vitest config according to the latest guidance.
Issue number: closes #4260
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.