Closed
Description
Summary
As reported by @shdq on Discord, the current iteration of the pre-commit
hook defined is not applying the eslint
fixes in the correct order, and instead it's doing so in the files already committed.
Why is this needed?
The expected behavior should be to lint the staged files instead and fix them before they are committed.
Which area does this relate to?
Automation
Solution
No response
Acknowledgment
- This request meets Lambda Powertools Tenets
- Should this be considered in other Lambda Powertools languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.