Skip to content
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

fix: TypeError custom override #1229

Merged
merged 3 commits into from
Feb 19, 2024
Merged

fix: TypeError custom override #1229

merged 3 commits into from
Feb 19, 2024

Conversation

dipsaus9
Copy link
Contributor

Status

Ready

Fix #1202

Description

If a custom mock is implemented we don't want a return type. This would be ideal to have. But, in the scenario of an enum, strict literal it is not possible to follow these strict types. Turning them off would be better in this scenario.

Todos

  • Tests (only added an empty object that should not give a type error)
  • Changelog Entry (unreleased) - not sure what to do?

Steps to Test or Reproduce

I added a extra test. Without the change the test would break

@melloware melloware added this to the 6.26.0 milestone Feb 19, 2024
@melloware melloware added the bug Something isn't working label Feb 19, 2024
@melloware melloware merged commit 4f95efb into anymaniax:master Feb 19, 2024
2 checks passed
@soartec-lab
Copy link
Collaborator

@dipsaus9
It seems like I didn't understand what you meant correctly, but after seeing this PR I understood. Thank you for the great changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mock TypeError custom override
3 participants