Our discourse sso plugin should include the timezone in the hash that's returned, so we can use it to show possible drill times. UnregisteredUser already expects it (though we could remove that if need be).
EDIT: I'd forgotten how discourse sso works. The omniauth-discourse plugin runs on the personnel server, and simply interacts with discourse. What discourse provides in a successful response is predefined, and editing that would require creating some sort of new discourse plugin.
So the options are:
Fetch the user's time zone from discourse when they sign in (via an additional api request)
Our discourse sso plugin should include the timezone in the hash that's returned, so we can use it to show possible drill times.UnregisteredUser
already expects it (though we could remove that if need be).EDIT: I'd forgotten how discourse sso works. The omniauth-discourse plugin runs on the personnel server, and simply interacts with discourse. What discourse provides in a successful response is predefined, and editing that would require creating some sort of new discourse plugin.
So the options are: