Maintenance: Remove the parser config parameter from Batch processor
Closed this issue · 2 comments
Summary
The parser integration feature in Batch processor is not fully completed yet. So, for the release today, we should remove the parser config option from the constructor so that it cannot be used.
Why is this needed?
The feature has still some work left to do, so prevent it from being released with today's release, we need this
Which area does this relate to?
Batch Processing
Solution
No response
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
Warning
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Warning
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.