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
I noticed in the Defining a Schema that it mentions using regular methods for resolvers. However, during testing, I encountered an error: NotImplementedError: Non static resolves are not supported yet.
Additionally, I found in the What's new in V1 section that it states: resolve_xxx(self, ...) - support resolve with (self) is dropped in favor of pydantic build-in functionality
Does this mean the old resolver method is no longer supported? If so, does the documentation need updating to reflect this change?
The text was updated successfully, but these errors were encountered:
It looked like a cool feature. I figure they might have dropped it in favor of using the context object? (Not sure if you can get the other attributes from it)
But the main thing for me is.. it could save you from adding @staticmethod to every resolver 😅 That's 1 less line every time.
I noticed in the Defining a Schema that it mentions using regular methods for resolvers. However, during testing, I encountered an error:
NotImplementedError: Non static resolves are not supported yet
.Additionally, I found in the What's new in V1 section that it states:
resolve_xxx(self, ...) - support resolve with (self) is dropped in favor of pydantic build-in functionality
Does this mean the old resolver method is no longer supported? If so, does the documentation need updating to reflect this change?
The text was updated successfully, but these errors were encountered: