What were you searching in the docs?
After adding functional APIs for all utilities as part of this parent issue (#2202) we should update our documentation to reflect these changes.
Is this related to an existing documentation section?
No response
How can we improve?
This issue suggests to create a "Usage Patterns" page similar to the TypeScript documentation (https://docs.aws.amazon.com/powertools/typescript/latest/getting-started/usage-patterns/).
Additionally, the individual pages of utilities should be update to highlight this new possibility of using a functional API. We can mention this during the installation instructions highlighting that AspectJ is only needed when using annotations but not for the functional interface.
Got a suggestion in mind?
No response
Acknowledgment
What were you searching in the docs?
After adding functional APIs for all utilities as part of this parent issue (#2202) we should update our documentation to reflect these changes.
Is this related to an existing documentation section?
No response
How can we improve?
This issue suggests to create a "Usage Patterns" page similar to the TypeScript documentation (https://docs.aws.amazon.com/powertools/typescript/latest/getting-started/usage-patterns/).
Additionally, the individual pages of utilities should be update to highlight this new possibility of using a functional API. We can mention this during the installation instructions highlighting that AspectJ is only needed when using annotations but not for the functional interface.
Got a suggestion in mind?
No response
Acknowledgment