add tenant example

[vinstah]

Test Plan

Checklist

• Docs updated

Screenshots

[kentcdodds]

This is great! Just one thing.

[kentcdodds]

I think this may be private:

Could you make it public?

[vinstah]

doh, public now!

[kentcdodds]

Thanks!

Unfortunately, it's hard to tell what changes are required for this example. The instructions say you should make a commit as soon as you initialize the project and then after you make your changes so people can see the difference between a standard epic stack project and one with the changes you make.

Could you do that please?

[vinstah]

Hi, yeah I'll update that

[vinstah]

Hi Kent,

I've updated it now

[kentcdodds]

Thanks!

I'm concerned the implementation is overly complicated. What do you think about doing this instead:

1. create a tenant model with an id and name
2. give all models a tenantId and relate them to the tenant (one-to-many relationship)
3. adjust queries to scope them to a specific tenantId (may require updating the routes to include the tenantId in the params)

I think that would be simpler than having a User, TenantUser, WorkspaceUser and Member all of which kinda feel like the same abstract concept to me. What do you think?

[vinstah]

Yeah they do seem to be sort of the same at the moment, though I chose to add extraction so when I want to query a WorkspaceUser I can simply do prisma.workspaceuser, a TenantUser is usually the admin of the tenant and manages subscription/payment, Members are the Individuals that belong to the Tenant.

It's a complex system that does need thorough documentation

[kentcdodds]

Ok, sounds good. Thanks!