You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issues like this pop up because we maintain a horrendous list of imports that needs to be updated any time a serializable field's type is exclusively imported in a TYPE_CHECKING block. Because they're only imported for the type checker, we get a name error when resolving the types unless we actually import it first.
I think the only solution is to move serialized field's type's out of TYPE_CHECKING blocks, but this will come with some tricky circular import issues.
The text was updated successfully, but these errors were encountered:
Issues like this pop up because we maintain a horrendous list of imports that needs to be updated any time a serializable field's type is exclusively imported in a
TYPE_CHECKING
block. Because they're only imported for the type checker, we get a name error when resolving the types unless we actually import it first.I think the only solution is to move serialized field's type's out of
TYPE_CHECKING
blocks, but this will come with some tricky circular import issues.The text was updated successfully, but these errors were encountered: