This repository has been archived by the owner on Jan 8, 2021. It is now read-only.

FpUserRegistrant/FpUserPartner Unification #3

Open

4 tasks

chgad opened this issue Apr 5, 2018 · 0 comments

Contributor

chgad commented Apr 5, 2018

Until now the Registrant and Partner are seperate Models in the Backend.
For Future Compatibility and more logical reasons we wish to :

remove the FpUserPartner model
implement an "in table" Relation between Users --> Future Partner Relations
introduce a new field is_partner
Transfer all bussines logic to the new scheme

The text was updated successfully, but these errors were encountered:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.