Using pydantic model's methods as field resolvers

[OlehDziuba]

Feature Request Type

• [ ] Core functionality
• [x] Alteration (enhancement/optimization) of existing feature(s)
• [ ] New behavior

Description

Using computable properties or methods of the pydantic model instead of strawberry.field

  class User(BaseModel):
      first_name: str
      last_name: str 

      def full_name(self, separator: str) -> str: 
          return f"{self.first_name}{separator}{self.last_name}"

@strawberry.experimental.pydantic.type(model=User, all_fields=True)
 class UserType: 
     pass

Now the scheme looks like this:

 type UserType{
   first_name: String!
   last_name: String!
 }

But it would be convenient to have a scheme that looks like

type UserType{
  first_name: String!
  last_name: String!
  full_name(separator: String!): String!
} 

Upvote & Fund

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.

[mecampbellsoup]

I imagine this is now solved by https://strawberry.rocks/docs/guides/accessing-parent-data...