Fix cross-module generics using forward refs#319
Open
kdkavanagh wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Hey @Fatal1ty, I hate to be a nag on these bug fix PRs, but is there any chance these could be merged soon? I'm blocked on ~all of these and am trying to avoid forking the repo/hanging my projects off that fork |
Owner
|
Hi @kdkavanagh I'm a little busy at work right now, but I'll find time this weekend to see all the PRs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Previously, mashumaro had an issue resolving forward references in module B when the field was declared in module A - it would only try to evaluate the forwardref inside module A's context