Maintenance: make ParsingOption name clearer in JMESPath utility

[dreamorosi]

Summary

Customer using the JMESPath utility can customize the way expressions are parsed by specifying options, for example they can extend the functions available.

Currently the option and corresponding type for this feature is called ParsingOption which is overly generic.

We should rename it to clarify what it does and where it comes from.

Why is this needed?

Because the utility is being consumed by other packages like Idempotency and because there's another upcoming utility called Parser.

Namespacing the type by using something like JMESPathParsingOptions would immediately make it clear where the option comes from and what it's for.

Which area does this relate to?

JMESPath

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.

[github-actions]

⚠️ COMMENT VISIBILITY 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 tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under v2.1.0 version!