feat: topOffers resolver

[zhengow]

Thank you for your contribution to the KodaDot Indexer.
👇 _ Let's make a quick check before the contribution.

PR type

• Bugfix
• Feature
• Refactoring

What's new?

• PR closes top offers resolver #45
• This PR is required for Top offers component  nft-gallery#3514

Before submitting Pull Request, please make sure:

• My contribution builds clean without any errors or warnings
• I've merged recent default branch -- main and I've no conflicts
• I've tried to respect high code quality standards
• I've didn't break any original functionality
• I've posted a screenshot of demonstrated change in this PR

Optional

• I've run the indexer and it hasn't failed
• I've changed schema and performed a migration
• I found edge cases

Screenshot

• My contribution is a resolver so I have pic from playground

[roiLeo]

would it not be missing LIMIT in query?

[zhengow]

would it not be missing LIMIT in query?

Yes, it should have.
But some questions:

1. Why offerStatsResolver doesn't have LIMIT?
2. How can I also return totalCount while return the top offers nft lists? Because if adding LIMIT in query, it should have pagination component which should know total amount.

[roiLeo]

1. Why `offerStatsResolver` doesn't have `LIMIT`?

It looks like offer query don't need LIMIT as it returns only numbers of rows (COUNT)
your topOffer query is returning data and it can be exponential (and potentially very resource-intensive)

2. How can I also return `totalCount` while return the top offers nft lists? Because if adding `LIMIT` in query, it should have pagination component which should know total amount.

Can't help you on that sorry :/
maybe try to get some inspiration frome events

[vikiival]

Please use limits :/