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
{{ message }}
This repository has been archived by the owner on Dec 8, 2017. It is now read-only.
In #10, we made users a foreign key on roles, but that doesn't feel quite right. Users and roles are separate, and should be combined inside of the acquisition. For example, one user may be the product lead on one project and a tech lead on another, but having an entry for every possibility feels a little heavy. This might involve customizing the User model.
The text was updated successfully, but these errors were encountered:
Are you saying that the Role class should include "Product Lead" and "Acquisitions Lead", and that there should be a separate class that combines the Role with the User?
Yeah, I think that's it. Customizing the User model is probably not a good idea.
However, I think I was also imagining the roles as something wider, which I'm not sure is necessary. What's in there now should work well, so I think this issue should just be a prompt to think about this once we've used the tool a bit.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In #10, we made users a foreign key on roles, but that doesn't feel quite right. Users and roles are separate, and should be combined inside of the acquisition. For example, one user may be the product lead on one project and a tech lead on another, but having an entry for every possibility feels a little heavy. This might involve customizing the User model.
The text was updated successfully, but these errors were encountered: