Skip to content
This repository has been archived by the owner on May 9, 2024. It is now read-only.

Expose the aws event #15

Closed
pdiazvargas opened this issue Feb 25, 2019 · 0 comments
Closed

Expose the aws event #15

pdiazvargas opened this issue Feb 25, 2019 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@pdiazvargas
Copy link
Contributor

What

While writing the documentation example I noticed that there are a few fields from the context, that minik is not currently exposing to the caller. For instance the StageVariables, these are values configured at the API Gateway level, that will never get passed in to the view.

This is the documentation of the fields in the event: https://docs.aws.amazon.com/lambda/latest/dg/eventsources.html#eventsources-api-gateway-request

How

Either keep a copy of the original event in the request so that a developer can write something like:

dev view():
    app.request.event.get('stageVariables')

Or implement a refactoring of the request object to load properties on demand.

Why

If a developer has a set of stage variables set and he's not able to access them, using minik would be frustrating.

@pdiazvargas pdiazvargas added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Feb 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant