Refactor validation logic to separate the function for finding operations that need a ValidationException.
#3722
Comments
github-merge-queue bot
pushed a commit
that referenced
this issue
Jun 28, 2024
…xception` (#3720) Refactor and define a separate function that returns a set of operation shapes that must have a supported validation exception shape in their associated errors list. This helps identify which type of `ValidationException` has been added to the operation shape's errors list. Closes: [3722](#3722) --------- Co-authored-by: Fahad Zubair <fahadzub@amazon.com> Co-authored-by: david-perez <d@vidp.dev>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The function validateOperationsWithConstrainedInputHaveValidationExceptionAttached uses a
Walkerto find all operation shapes that should have aValidationExceptionin the errors list, then filters out the ones that don't have it to raise an error.The logic to find all such operations that need a
ValidationExceptionshould be defined as a separate function. This will be helpful in other parts of the codebase that might need to determine which kind ofValidationExceptionhas been added to operations.The text was updated successfully, but these errors were encountered: