-
Notifications
You must be signed in to change notification settings - Fork 46
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: Populate permits from metadata #377
Conversation
! You must be a core team member, or an administrator to start this task |
Unused exports (1)
|
|
@zugdev The PR got closed, can I reopen it or do I have to be assigned to the task? |
} | ||
|
||
// Using our metadata system we can easily GraphQL query for permits. | ||
const permits = (await supabase.from("permits").select("*").eq("beneficiary_id", githubId)).data; |
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 very wrong. Permits should load from GitHub not supabase
// TODO | ||
owner: "0x70997970C51812dc3A010C7d01b50e0d17dc79C8", | ||
// TODO | ||
tokenAddres: "0xe91D153E0b41518A2Ce8Dd3D7944Fa863463a97d", | ||
tokenType: "ERC20" |
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.
Doesn't make sense should be read from permits
// limit to previous 100 results or whatever is the max that GraphQL can return in a single shot | ||
// check if they have already been claimed, if so, discard | ||
// if unclaimed permits are found, import into the UI (we should already support multiple permits to be loaded in the UI) |
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.
Logic isn't here
Resolves #368