Users Position commands #218
Open
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
Contributor
Author
|
Will convert to draft for now, usage rn > |
Contributor
Author
|
all three: 
|
Contributor
Author
|
More fields could be added, you can drop suggestion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Issue #208
I was having an issue with some fields on thursday, but it has now been fixed. I was supposed to drop a comment then.
Getting the user position requires at least a chainId parameter. This is because
UserPositionsRequestFilter uses @oneOfif no chainId is provided, the API revertsUnexpectedError: [GraphQL] Bad user input - You must supply at least 1 chain idI was thinking about whether all available chain IDs could be used when none is provided (for example, by retrieving them through spokes), or maybe leave it as it's now(required atleast one chain id)