Doing delete Object would fail on the two trigger assertions.
These were to prevent mistakes, but these actions should
only happen in one spot in the schema or app code.
So I'm fine dropping them to make deletes more ergonomic.
FWIW both of these should work from my perspective
with delete Object so maybe they are bugs.
Deleting Partner or Organization deletes the other.
Deleting Language/Project/Org deletes their ProjectContext
Deleting Scripture::VerseRanges are allowed if their Scripture::Collection is being deleted too
Marking migration files as generated so GitHub doesn't render them by default (or count them in diff stats)
delete Object
would fail on the two trigger assertions.delete Object
so maybe they are bugs.Partner
orOrganization
deletes the other.Language
/Project
/Org
deletes theirProjectContext
Scripture::VerseRanges
are allowed if theirScripture::Collection
is being deleted too