Skip to content

Maintenance: add Middy license to repository notice #1248

Closed
@saragerion

Description

@saragerion

What were you searching in the docs?

As @dreamorosi correctly described in this PR, we resolved to temporarily importing the middy types

This workaround is not the best solution. It's supposed to be temporary and will be removed and replaced with a better solution with v2, where we will restore the middy core import.

Other than that, we should credit Middy in our license notice.

Is this related to an existing documentation section?

https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/LICENSE-THIRD-PARTY

How can we improve?

N/A

Got a suggestion in mind?

N/A

Acknowledgment

  • I understand the final update might be different from my proposed suggestion, or refused.

Metadata

Metadata

Assignees

Labels

completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions