Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(pool_manager): pools query improvement #372

Merged
merged 4 commits into from
Jul 2, 2024

Conversation

kerber0x
Copy link
Contributor

@kerber0x kerber0x commented Jul 2, 2024

Description and Motivation

This PR modifies the Pool query on the pool manager so that it returns a list of pools if desired. This can help frontends list all the pools in the contract. It offers pagination.

Related Issues


Checklist:

  • I have read Migaloo's contribution guidelines.
  • My pull request has a sound title and description (not something vague like Update index.md)
  • All existing and new tests are passing.
  • I updated/added relevant documentation.
  • The code is formatted properly cargo fmt --all --.
  • Clippy doesn't report any issues cargo clippy -- -D warnings.
  • I have regenerated the schemas if needed cargo schema.

@kerber0x kerber0x force-pushed the feat/pools-query branch from 1a6462c to 4d7f83e Compare July 2, 2024 14:24
@kerber0x kerber0x changed the base branch from release/v2_contracts to feat/integration-tests-crate July 2, 2024 14:27
Copy link
Contributor

@nseguias nseguias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGMT

@kerber0x kerber0x force-pushed the feat/pools-query branch from edb84a7 to fdc26a5 Compare July 2, 2024 15:19
@kerber0x kerber0x merged commit 00f346b into feat/integration-tests-crate Jul 2, 2024
3 of 5 checks passed
@kerber0x kerber0x deleted the feat/pools-query branch July 2, 2024 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants