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
Aliasing a concrete type causes a RecursionError for identity map #159
Labels
bug
Something isn't working
Comments
Also, thank you for this wonderful package! |
Thanks for the detailed description @mrogaski I'll take a look at this. |
I've just released 1.3.1 that should fix the regression. Let me know if it doesn't. Thanks again for the detailed report. |
I can confirm it's fixed for our use case. (We're allowing a type mapping to be overridden in configuration, but setting it to the identity map by default.) |
meadsteve
added a commit
that referenced
this issue
Aug 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that the change to how the
Alias.skip_definitions
flag is used in #150 introduced a regression. If an alias maps a type to itself, any resolution to the alias will raise a RecursionError.This is Python 3.9.4 and Lagom 1.3.0.
Ultimately, this isn't a huge issue. But it seems that a guard condition is merited so the identity map can be allowed.
The text was updated successfully, but these errors were encountered: