Allow adding a foreign key to Exensible Model

Alternative and generalised approach to the requirement that AlekSIS-App-Chronos!61 (closed) tries to fulfill.

Closes AlekSIS-App-Chronos!61 (closed).

Depends on !306 (merged).

Yet to be tested, but please review the general idea, @hansegucker, and decide whether it matches your use case from the linked MR in Chronos.

changed the description

added 1 commit

• 6d843009 - Use more specific helper methods

Compare with previous version

The semantics are more that of a OneToOneField right now. I will fix this.

mentioned in merge request AlekSIS-App-Chronos!61 (closed)

resolved all threads

added 82 commits

• 6d843009...d801f952 - 80 commits from branch master
• 353474a4 - Merge branch 'master' into feature/extensible-model-fk
• 34ecd209 - Fix typo

Compare with previous version

added 2 commits

• 594508fa - Fix typo
• 5514e0ab - Make foreign key reverse on extensible model behave like foreign key

Compare with previous version

unmarked as a Work In Progress

added 11 commits

• 5514e0ab...edc5c39d - 9 commits from branch master
• df039094 - Merge branch 'master' into feature/extensible-model-fk
• 9202d5f8 - Fix syntax errors and property creation in foreign_key helper

Compare with previous version

mentioned in issue AlekSIS-App-Chronos#89 (closed)

enabled an automatic merge when the pipeline for 9202d5f8 succeeds

canceled the automatic merge

mentioned in commit 75256e08

merged

mentioned in merge request !378 (merged)