You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
am29d opened this issue
Mar 7, 2024
· 2 comments
· Fixed by #2179
Assignees
Labels
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)parserThis item relates to the Parser Utility
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.
The text was updated successfully, but these errors were encountered:
am29d
added
triage
This item has not been triaged by a maintainer, please wait
internal
PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
labels
Mar 7, 2024
am29d
added
parser
This item relates to the Parser Utility
completed
This item is complete and has been merged/shipped
and removed
triage
This item has not been triaged by a maintainer, please wait
labels
Mar 7, 2024
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)parserThis item relates to the Parser Utility
Summary
We currently don't export subpaths for
envelopes
,schemas
andtypes
in ourpackage.json
, and we should add them, so customers can import them.Why is this needed?
So customers can granularly import schemas and envelopes following the same standard that we have introduced with in v2.
Which area does this relate to?
No response
Solution
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: