fix(frontend): queryOptions in UserSelection being a nop#1409
Merged
Conversation
c0rydoras
marked this pull request as ready for review
July 23, 2026 08:40
there is one use of `UserSelection` with `@queryOptions={{hash is_reviwer=1}}`
before this change, passing `@queryOptions` wouldn't do anything
c0rydoras
force-pushed
the
fix/frontend/user-selection
branch
from
July 23, 2026 09:03
7efe609 to
a50c8f8
Compare
c0rydoras
enabled auto-merge (squash)
July 23, 2026 09:04
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
2 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.
there is one use of
UserSelectionwith@queryOptions={{hash is_reviwer=1}}before this change, passing@queryOptionswouldn't do anything