You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I added a UnderlyingPostionsValue method to help with some tests, but realized this would be really useful to expose as a query.
Suggested Design
The underlying logic is already completed in the UnderlyingPositionsValue method. One just has to wire this up to a respective query to expose via gRPC.
Acceptance Criteria
localosmosis tested against existing positions and the value returned makes sense. Preferable one in range, one above the current price, and one below the current price.
The text was updated successfully, but these errors were encountered:
hey @czarcas7ic! I have a question on this one: should it be possible to provide a list of positions in CLI when querying [1], or should it only take a single position id as an argument [2]?
Background
See the following comment for context #6623 (comment)
I added a UnderlyingPostionsValue method to help with some tests, but realized this would be really useful to expose as a query.
Suggested Design
The underlying logic is already completed in the UnderlyingPositionsValue method. One just has to wire this up to a respective query to expose via gRPC.
Acceptance Criteria
localosmosis tested against existing positions and the value returned makes sense. Preferable one in range, one above the current price, and one below the current price.
The text was updated successfully, but these errors were encountered: