Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature request: JMESPath parser #2211

Closed
1 of 2 tasks
dreamorosi opened this issue Mar 12, 2024 · 2 comments · Fixed by #2266
Closed
1 of 2 tasks

Feature request: JMESPath parser #2211

dreamorosi opened this issue Mar 12, 2024 · 2 comments · Fixed by #2266
Assignees
@dreamorosi
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 jmespath This item relates to the JMESPath Utility

Comments

@dreamorosi
Copy link
Contributor

Use case

As part of the JMESPath utility implementation we need to define a parser.

The parser is the main orchestrator component and uses a lexer (#2205), AST (#2210), and tree interpreter (#2209) to tokenize, abstract, and traverse the JMESPath expression and produce a result.

Solution/User Experience

All types, classes, and functions should be documented and exposed to customers via API docs.

Alternative solutions

No response

Acknowledgment

Future readers

Please react with 👍 and your use case to help us understand customer demand.
@dreamorosi dreamorosi added feature-request This item refers to a feature request for an existing or new utility confirmed The scope is clear, ready for implementation jmespath This item relates to the JMESPath Utility labels Mar 12, 2024
@dreamorosi dreamorosi self-assigned this Mar 12, 2024
@dreamorosi dreamorosi moved this from Triage to Backlog in Powertools for AWS Lambda (TypeScript) Mar 12, 2024
@dreamorosi dreamorosi mentioned this issue Mar 12, 2024
Merged
9 tasks
@dreamorosi dreamorosi moved this from Backlog to Pending review in Powertools for AWS Lambda (TypeScript) Mar 21, 2024
@dreamorosi dreamorosi mentioned this issue Mar 21, 2024
Merged
9 tasks
@dreamorosi dreamorosi linked a pull request Mar 21, 2024 that will close this issue
feat(jmespath): add parser component #2266
Merged
9 tasks
@github-project-automation github-project-automation bot moved this from Pending review to Coming soon in Powertools for AWS Lambda (TypeScript) Mar 27, 2024
@github-actions GitHub Actions
Copy link
Contributor

⚠️ 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 github-actions bot added pending-release This item has been merged and will be released soon and removed confirmed The scope is clear, ready for implementation labels Mar 27, 2024
@github-actions GitHub Actions
Copy link
Contributor

This is now released under v2.0.4 version!

@github-actions github-actions bot added completed This item is complete and has been merged/shipped and removed pending-release This item has been merged and will be released soon labels Apr 10, 2024
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dreamorosi dreamorosi

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 jmespath This item relates to the JMESPath Utility
Projects
Powertools for AWS Lambda (TypeScript)
Status: Shipped
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(jmespath): add parser component aws-powertools/powertools-lambda-typescript
1 participant
@dreamorosi