What about also storing/exposing current_request ?
It would for instance allow to use django's message framework from the model layer (obvisously violating MVC architecture but those who value architecture principles over pragmatism are probably not around this repo :-) )
I think it would be pretty easy to implement in a backwards-compatible way.
There are some other packages that offer this (django-current-request, django-crum), but they seem unmaintained, and the scope is very close to this one, why not join efforts ?
If this is accepted, I can probably contribute a PR.
Let me know what you think.
Thanks for the package !!
What about also storing/exposing
current_request?It would for instance allow to use django's message framework from the model layer (obvisously violating MVC architecture but those who value architecture principles over pragmatism are probably not around this repo :-) )
I think it would be pretty easy to implement in a backwards-compatible way.
There are some other packages that offer this (django-current-request, django-crum), but they seem unmaintained, and the scope is very close to this one, why not join efforts ?
If this is accepted, I can probably contribute a PR.
Let me know what you think.
Thanks for the package !!