Feature request: add TransferFamilySchema
to Parser
#3518
Labels
completed
This item is complete and has been merged/shipped
feature-request
This item refers to a feature request for an existing or new utility
good-first-issue
Something that is suitable for those who want to start contributing
parser
This item relates to the Parser Utility
Use case
Powertools for AWS Lambda (Python) recently added a Parser built-in schema for customers who work with Transfer Family (aws-powertools/powertools-lambda-python#5903). We should do the same and add a schema to our version as well.
Note
If you're interested in picking this up please leave a comment to claim it. A maintainer will assign the issue to you and help you with reviewing your PR. Likewise, if you have any questions before starting, feel free to leave a comment below.
Solution/User Experience
Customers should be able to use the built-in schema the same way as they use all the other built-in ones. For example:
To work on the issue, we should:
packages/parser/src/schemas/transfer-family.ts
TransferFamilyEvent
type inpackagesparser/src/types/schema.ts
& correspondingpackagesparser/src/types/index
(you can import the schema directly from thepackages/parser/src/schemas/transfer-family.ts
file rather than adding it to the barrel file - which we want to move away from)packages/parser/package.json
exports here andtypesVersions
herepackages/parser/tests/events/transfer-family/base.json
and write unit tests following the same style and conventions of the ones for other schemas, for examplepackages/parser/tests/unit/schema/alb.test.ts
Alternative solutions
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: