-
Notifications
You must be signed in to change notification settings - Fork 153
Bug: Declared Idempotency Packages Do Not Match Repo Structure #1486
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
Comments
Hi @brianhyder thank you for reporting this. I'll be adding the Middy middleware in the next couple of hours and double-check the other one. When I was doing the tests I checked on macOS & Linux OS and was initially having case-sensitive errors on that file, however I thought I fixed them. I'll check again. |
I have just pushed the changes & opened the PR, both issues should be fixed and I have also added an export for the types that was not present, so you couldn't import the types in your code if you wanted to do so. Let me know if you have any chance to test it before I merge it and confirm that it fixes the issue. |
Thank you, I should be able to test it out in the next few hours. |
|
Expected Behaviour
The package should allow requiring/importing the modules as described in the package.json for idempotency.
Current Behaviour
The packge.json describes exports for the root of the module, persistence, and the dynamodb persistence layer. However, the capitalization of the dynamodb persistence layer class is incorrect (
DynamoDbPersistenceLayer
=>DynamoDBPersistenceLayer
).The package.json is also missing the now available
middleware
module.Code snippet
Steps to Reproduce
Possible Solution
Update the package.json to have the correct capitalization and add the middle ware module to the
exports
declaration.Powertools for AWS Lambda (TypeScript) version
latest
AWS Lambda function runtime
18.x
Packaging format used
npm
Execution logs
No response
The text was updated successfully, but these errors were encountered: