Change validation exceptions to unchecked exceptions #141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
With the release of version 4, we introduced validation features aimed at providing immediate feedback on invalid properties and metrics. This proactive approach was designed to save customers time by eliminating the need to troubleshoot missing metrics in CloudWatch. Initially, we implemented these validations as checked exceptions to ensure they were explicitly handled.
However, after careful consideration of recent customer feedback, we recognize that this design choice may not align with all use cases. To offer a more flexible integration, we are transitioning our validation exceptions from checked to unchecked. This change is intended to streamline error handling and improve the overall developer experience.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.