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

andypost’s picture

tim.plunkett’s picture

Wouldn't we actually want to make the current_user service synthetic?

damiankloip’s picture

Hmm, 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.

catch’s picture

Issue summary: View changes
Status: Active » Closed (duplicate)