-
Notifications
You must be signed in to change notification settings - Fork 39
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
Typings mismatches between client mock and AWS typings #246
Comments
Seeing the same thing. I worked around this by not passing the mocks into the methods. Before
After
Works the same but passes TSC. |
@tylerd-canva Thank you, that worked! I still feel the typings mismatch is an issue but I'm happy to close this issue for now since there's a viable workaround. |
Personally I'd leave it open as I'd much prefer the approach we both tried initially :P |
I spoke to soon! The workaround certainly works for scenarios where only one instance of a client is needed in a set of tests, but not when more than one are needed. I'll leave it open in that case since the original approach serves a valid purpose.
I'm with you on that one 😄 |
Checklist
Bug description
Hello 👋 !
I'm having troubles with typings mismatches between the AWS client mocks vs the AWS client typings themselves, even after trying out everything in the caveats docs.
I'm currently using an
AthenaClient
and aGlueClient
in my code and passing a mock for either to a function which expects the respective clients shows me typings errors like:and
The specific package versions I'm using:
I've also verified that I have only one version of
@smithy/types
at the moment:Any help would be appreciated, thank you!
Reproduction
The text was updated successfully, but these errors were encountered: