Skip to content
New issue

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

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

Already on GitHub? # to your account

docs(lambda-go): fix typos #29567

Merged
merged 2 commits into from
Mar 21, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions packages/@aws-cdk/aws-lambda-go-alpha/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,15 +29,15 @@ Define a `GoFunction`:

```ts
new go.GoFunction(this, 'handler', {
entry: 'app/cmd/api',
entry: 'lambda-app/cmd/api',
});
```

By default, if `entry` points to a directory, then the construct will assume there is a Go entry file (i.e. `main.go`).
Let's look at an example Go project:

```bash
lamda-app
lambda-app
├── cmd
│   └── api
│   └── main.go
Expand Down Expand Up @@ -244,7 +244,7 @@ all of your functions if anything changes, then `AssetHashType.SOURCE` will prob
For example, if my app looked like this:

```bash
lamda-app
lambda-app
├── cmd
│   └── api
│   └── main.go
Expand All @@ -263,7 +263,7 @@ should trigger a new deploy, I could specify `AssetHashType.SOURCE`.
On the other hand, if I had a project that deployed multiple Lambda functions, for example:

```bash
lamda-app
lambda-app
├── cmd
│   ├── api
│   │   └── main.go
Expand Down