-
Notifications
You must be signed in to change notification settings - Fork 4
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
refactor: do not index NFTs for potentially "full" collections #101
Conversation
public function isPotentiallyFull(): bool | ||
{ | ||
// If there is no supply or if the NFTs for the collection haven't been indexed, we know for sure it's not full... | ||
if ($this->last_indexed_token_number === null || $this->supply === null) { |
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.
Please note that we are already filtering out collections with supply=null
: https://app.clickup.com/t/85zu0hdha
It's worth double-checking to ensure that we are not excessively filtering out collections.
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.
wdym? we're filtering collections where the supply is not null so this check ($this->supply === null
) will always be false and therefore irrelevant in this case
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.
with the current way we call this isPotentiallyFull
method we won't ever pass it a collection with a null
supply, but for reliability I'd keep the check in case something calls it without the withAcceptableSupply
scope as it avoids assumptions here
Summary
https://app.clickup.com/t/861nbbgp1
Checklist