Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
In #2076411: Remove the request scope from the current user service we removed the request scope from the current user service. That should unblock some other patches that remove global $user, but it also masks other bugs where systems are trying to get a current user outside of the request scope.
So.. this issue is for adding it back in - once those conversions are in, we should be able to put a revert of #2076411: Remove the request scope from the current user service up here to see what breaks.
Comments
Comment #1
andypostRelated bug in simpletest #2102539: Current user service should be updated in drupalLogin() and drupalLogout()
Comment #2
tim.plunkettWouldn't we actually want to make the current_user service synthetic?
Comment #3
damiankloip CreditAttribution: damiankloip commentedHmm, I don't think so? As the current_user comes from the authentication manager service. So this would need to be called outside of the container on every request to populate current_user, which would be weird.
Comment #4
catchWill get resolved by #2180109: Change the current_user service to a proxy hopefully.