Refactor userstatus

[nrbnlulu]

resolve #250

[gqlauthbot]

Release type: minor

BREAKING CHANGES:
This release refactors the way user status is managed.
now it is a field inside your user model meaning you would need to extend
our Abstract model.

[ferndot]

@nrbnlulu is it possible to use strawberry without the status feature? My team already handles that and does not wish to introduce a new model or field.

[nrbnlulu]

@nrbnlulu is it possible to use strawberry without the status feature? My team already handles that and does not wish to introduce a new model or field.

I'd hope so.. this status thing is something I inherit from the graphene package..
I don't have time at the moment to remove this...

[ulgens]

@nrbnlulu Do you remember how much of these changes are directly related to the user status? I can try to rebase and resolve conflicts, but it looks like it does a bit more than #250

[nrbnlulu]

@nrbnlulu Do you remember how much of these changes are directly related to the user status? I can try to rebase and resolve conflicts, but it looks like it does a bit more than #250

I think most don't. if you'r goal would be just removing the user_status table I would start fresh 🙃

[ulgens]

I'm not looking to remove it but a way to disable it. I don't have the time to handle it right now but I can revisit it later, depending on the another project's timeline that uses this package.