While we do somewhat mention this stuff, and we do have part in docs that tells how to populate a user in Prisma query, the fact is that this is just quite complex, and it is not easy for a user to figure out how to best go around this.
In this piece of docs, we should give them guidance on how to deal with User data.
We should point to them that they can, during signup, by using userSignupFields, store fields directly on the User. We should give some examples, explain when it should be done, when not.
We should demonstrate how to fetch the data about user in different situations -> how to do it when they have AuthUser available, vs how to do it when they want to populate user in Prisma query (related: https://github.com/wasp-lang/wasp/issues/2033).
While we do somewhat mention this stuff, and we do have part in docs that tells how to populate a user in Prisma query, the fact is that this is just quite complex, and it is not easy for a user to figure out how to best go around this.
In this piece of docs, we should give them guidance on how to deal with User data. We should point to them that they can, during signup, by using
userSignupFields, store fields directly on theUser. We should give some examples, explain when it should be done, when not. We should demonstrate how to fetch the data about user in different situations -> how to do it when they have AuthUser available, vs how to do it when they want to populateuserin Prisma query (related: https://github.com/wasp-lang/wasp/issues/2033).