-
Notifications
You must be signed in to change notification settings - Fork 15
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(1165) : collector whale entity + resolver #87
Conversation
MSghais
commented
May 22, 2022
- Create an Entity Collector
- Add schema
- Resolver collectorTable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand why you need both cache and resolver?
nooooo :D |
Ah excuse me, about what ? |
The cache implemetation was better/ preffered over resolver imo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.
It's written in this commit 1e13053 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, need to test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks oki may @petersopko can test ? 🥺
Sir we tried your impl but seems like the query does not return any results |
Hi, actually I used the collectorTable for the pagination in the frontend. Because the cache update is pretty long, and we need a refresh and last data in the UI with pagination, that's why I used the resolver. |
Yeah but resolver is pretty heavy for the indexer :) and we have a couple of outages (check #88 ) |
YOLO |
Looks like YOLO broke rubick ;D |