feat: Add Support wallet priority field in API and GraphQL #4391
Conversation
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
brunomiguelpinto
force-pushed
the
feat-multiple-wallet-load
branch
from
582013c to
7a2a1be
Compare
brunomiguelpinto
force-pushed
the
feat-multiple-wallet-load
branch
from
bfcafc4 to
488973a
Compare
brunomiguelpinto
changed the title
vincent-pochet
approved these changes
Sep 26, 2025
brunomiguelpinto
force-pushed
the
feat-multiple-wallet-load
branch
2 times, most recently
from
5fc46e0 to
92a121b
Compare
lovrocolic
approved these changes
Oct 8, 2025
annvelents
reviewed
Oct 8, 2025
annvelents
approved these changes
Oct 8, 2025
brunomiguelpinto
force-pushed
the
feat-multiple-wallet-load
branch
2 times, most recently
from
f633a07 to
4b2c778
Compare
brunomiguelpinto
force-pushed
the
feat-multiple-wallet-load
branch
from
da17b32 to
05cbfc9
Compare
floganz
added a commit
that referenced
this pull request
Dec 9, 2025
## Context We’re introducing the priority field to wallets to support custom execution or display ordering. This PR builds on the base work from #4391, which added the field to the Wallet model and exposed it via the API. The goal of this PR is to implement the logic that uses the priority value when handling wallets — for example, when determining which wallets to apply or process first. ## Description This PR includes: • Logic to order wallets by priority (and created_at as a secondary key). • Ensures active_wallets_in_application_order returns wallets in the correct priority sequence. • Updates any internal wallet processing to respect the defined order. This builds directly on the foundation laid in PR #4391 and assumes the priority field and its validations are already in place. --------- Co-authored-by: Miguel Pinto <darkymiguel@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
We’re introducing the priority field to wallets to allow custom ordering. This will enable better control over the execution or display order of wallets in various scenarios.
Description
This PR adds support for the priority attribute in the Wallet model. The changes include:
• Added priority field with default value 50 if none is provided.
• Validation to ensure priority is within the range of 1 to 50.
• API support: priority is now accepted and returned in REST endpoints.
• GraphQL support: added priority to the relevant types and mutations.
Using the new field its on this pr #4401