refactoring: avoid using negatives in sign-in gate's behaviour names#14281
Merged
refactoring: avoid using negatives in sign-in gate's behaviour names#14281
Conversation
github-actions
bot
removed
the
run_chromatic
tomrf1
approved these changes
Jul 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This introduces a refactoring to help understanding sign-in gate behaviour, something that is going to become important in a coming change.
What we do here is moving from the dichotomy ( dismissible / non dismissible ) or the dichotomy ( mandatory / non mandatory ) to the more natural, and which avoid potentially misleading negations ( dismissible / mandatory ).
Companion SDC PR: guardian/support-dotcom-components#1399