Skip to content

Conversation

@dumbmoron
Copy link
Member

this check was mostly intended to not break services access for pre-onboarding users. onboarding was introduced a long time ago (way before pre-0.0.1), so this is not a real concern anymore.

it was still possible to make ShouldAccessServices() return true by toggling services.enabled off and on in onboarding; this change should make it so that it's not possible anymore (meaning the user has to navigate to the next step before services are truly enabled).

For your pull request to not get closed without review, please confirm that:

this check was mostly intended to not break services access for
pre-onboarding users. onboarding was introduced a long time ago
(way before pre-0.0.1), so this is not a real concern anymore.

it was still possible to make ShouldAccessServices() return `true`
by toggling services.enabled off and on in onboarding; this change
should make it so that it's not possible anymore (meaning the user
has to navigate to the next step before services are truly enabled).
@dumbmoron dumbmoron requested a review from wukko February 1, 2026 23:00
@wukko wukko merged commit af7ab99 into main Feb 2, 2026
7 checks passed
@wukko wukko deleted the remove-prefpath-services branch February 2, 2026 06:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants