-
-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Query issue fix #414
Query issue fix #414
Conversation
Oh i've just seen what you mean, in our middleware we dont even call the additional fetch for profile. Maybe it's somewhere else. I'll check it out now, i could've swore it was here |
Ah this is what I was thinking of https://github.com/TreyWW/MyFinances/blob/main/backend/models.py#L41 |
Problem is that both With this changes we don't get double query issue and user profile is also accessible in |
Amazing. Does this pass all tests still and everything visually work on the site? Just wondering if any Django packages use the middleware or if they will automatically move over to our new one |
Yes it was passing tests on my machine and on website everything work as intended. As for I will fix that mypy error and will push that PR. |
Thanks @Domejko, really appreciate the support recently! |
Description
Regarding #267
"django.contrib.auth.middleware.AuthenticationMiddleware"
with"backend.middleware.CustomUserMiddleware"
Checklist
djLint-er on any new code
(checks
will
fail without)
changes
What type of PR is this?
Added/updated tests?
Related PRs, Issues etc