You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering, if we can use protected instead of private function then people can easily extends the Timezone and customize to their need.
Also, Can we extract the obtaining of the time zone in another class which will be responsible for assigning the time zone to the user (the user could be passed in the constructor and if not then we will use the Auth::user() )?
This will allow us to assign the time zone to the user without necessarily listening to the authentication event.
laravel-timezone/src/Timezone.php
Line 51 in 20ea12b
I'm wondering, if we can use protected instead of private function then people can easily extends the Timezone and customize to their need.
Also, Can we extract the obtaining of the time zone in another class which will be responsible for assigning the time zone to the user (the user could be passed in the constructor and if not then we will use the Auth::user() )?
This will allow us to assign the time zone to the user without necessarily listening to the authentication event.
laravel-timezone/src/Listeners/Auth/UpdateUsersTimezone.php
Line 50 in 20ea12b
The text was updated successfully, but these errors were encountered: