Skip to content

Conversation

cnaples79
Copy link

Summary

Partially addresses #1016 by marking a small set of public enums as so that downstream exhaustive matches remain forward-compatible as event shapes evolve.

Changes

  • lambda-events (DynamoDB): , , , , .
  • lambda-http: , , .

These types are likely to gain additional variants over time. Making them non-exhaustive reduces semver churn at the cost of requiring a wildcard match in consumers.

This is intentionally a minimal first step to validate appetite and direction; happy to expand the scope across crates in follow-ups or adjust the target set.

…s#1016)

- lambda-events (dynamodb): StreamViewType, StreamStatus, SharedIteratorType, OperationType, KeyType
- lambda-http: PayloadError, JsonPayloadError, FormUrlEncodedPayloadError

These enums are likely to grow; marking them non_exhaustive helps avoid semver hazards for downstream consumers who pattern-match exhaustively.
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.

1 participant