Closed spaceraccoon closed 6 years ago
@duhaime As far as I can tell there is no one-to-many relationship expressed in the current user
and building
models. Does this look right?
@spaceraccoon I'm not quite sure what you mean. The initial app requirements had a simple user model--only admins could create/edit buildings, and only superadmins could appoint admins. There was no notion of a user-building relationship beyond the simple rights model described above. Does this answer your question?
Yep that answers my question, thanks. I might have to run a database migration in this case as they want for non-admins to be able the create buildings and edit the buildings they have created, requiring some sort of relationship.
On Feb 3, 2018, at 11:40 PM, Douglas Duhaime notifications@github.com wrote:
@spaceraccoon I'm not quite sure what you mean. The initial app requirements had a simple user model--only admins could create/edit buildings, and only superadmins could appoint admins. There was no notion of a user-building relationship beyond the simple rights model described above. Does this answer your question?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
DB models and backend support updated in #313
@spaceraccoon Sounds good!
Non-admin users should be able to create buildings and edit the buildings they've created.
building
model should include acreator
property and theuser
model should include abuildings
property. This requires a DB migration./buildings/update
route need to be modified