fix filters in PricelistsSearcher - #51
Merged
Merged
Conversation
vaneck237
approved these changes
Feb 2, 2026
Blue-B-code
force-pushed
the
feature-35459
branch
from
July 21, 2026 16:01
244fb26 to
8f407c9
Compare
zikani03
marked this pull request as draft
July 30, 2026 10:09
Blue-B-code
marked this pull request as ready for review
July 31, 2026 14:57
zikani03
approved these changes
Aug 12, 2026
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
4 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.
Description
This PR fixes an issue in the medical pricelist module where the frontend could generate GraphQL queries containing multiple location_Uuid arguments (for example when both region and district filters were selected).
Because the backend only supports a single location_Uuid, such queries resulted in the GraphQL error:
There can only be one argument named "location_Uuid".
The fix introduces a centralized filter-building logic that guarantees only one location_Uuid is sent per request, following a clear business rule:
district selection always takes precedence over region selection.
The user interface behavior was also adjusted to prevent conflicting selections and ensure predictable filtering behavior, without requiring any backend changes.
Type of Change
Related Issue(s) / Task(s)
Demo
before
after
Checklist