Skip to content

Use a less abstract Lambda handler example #292

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.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

a-h
Copy link

@a-h a-h commented Jul 17, 2021

The first example in the documentation of how to structure a handler is (I think!) a rare use case. It's much more likely that someone writing a Lambda function will be triggering it via an AWS service than with a string or custom type.

As it stands, the documentation has the events package as a footnote.

By moving the events package into the example code, the package is much more discoverable. In your IDE, you can hit events. and see a list of all the available request and response types.

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The first example in the documentation of how to structure a handler is (I think!) a rare use case. It's much more likely that someone writing a Lambda function will be triggering it via an AWS service than with a string or custom type.

As it stands, the documentation has the `events` package as a footnote.

By moving the `events` package into the example code, the package is much more discoverable. In your IDE, you can hit `events.` and see a list of all the available request and response types.
Copy link

@clarozino411 clarozino411 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

doc_source/golang-handler.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants