-
Notifications
You must be signed in to change notification settings - Fork 560
CloudWatchEvent should be renamed #479
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
Labels
Comments
Maybe a type alias would do here. As far as I know the structure of these events hasn't changed, just the branding. |
mateusmarquezini
added a commit
to mateusmarquezini/aws-lambda-go
that referenced
this issue
Dec 17, 2023
mateusmarquezini
added a commit
to mateusmarquezini/aws-lambda-go
that referenced
this issue
Dec 17, 2023
mateusmarquezini
added a commit
to mateusmarquezini/aws-lambda-go
that referenced
this issue
Dec 19, 2023
mateusmarquezini
added a commit
to mateusmarquezini/aws-lambda-go
that referenced
this issue
Dec 22, 2023
mateusmarquezini
added a commit
to mateusmarquezini/aws-lambda-go
that referenced
this issue
Dec 23, 2023
bmoffatt
pushed a commit
that referenced
this issue
Jan 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I think because the documentation suggests using EventBridge over CloudWatchEvent, I thought that it is better to rename CloudWatchEvent to something that includes EventBridge maybe?
The text was updated successfully, but these errors were encountered: