-
Notifications
You must be signed in to change notification settings - Fork 43
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
F/OS-1224 Multisig approvers not appearing in past proposals #575
Conversation
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.
let some comments
Since there is a branch for removing all plugins, multisig included, f/split-linting, not sure if this should be done only in this repo |
Yes, this should also be done in the split repo, but i wanted to first get the fix reviewed and then aply it also to the other repo |
Co-authored-by: Jordan <[email protected]>
@clauBv23 I fixed the lint missues that you mentioned, I also took the librety some others that popped up when I ran yarn lint. I also updated the description in the |
* fix: multisig members not appearing in past proposals * wip * chore: update schema and methods * Update packages/subgraph/schema.graphql Co-authored-by: Jordan <[email protected]> * style: fix lint warnings * docs: improve graphql schema comments --------- Co-authored-by: Jordan <[email protected]>
Description
Some approvers did not appear as approvers on past proposals after they've been removed from the multisig because the entity for the multisift members and approvers was related.
This fixes this issue using the solution discussed here: https://www.notion.so/aragonorg/Subgraph-Bug-Approvers-Query-Breaks-Multisig-Subgraph-d783e196ba464595974ba2a9d2dac80a#5ca1bd831bbd4dc191dd8fb0d4360e8f
Task ID: OS-1224
Playground: https://subgraph.satsuma-prod.com/aragon/osx-test-members-bug-mainnet/version/5/playground
Type of change
See the framework lifecycle in
packages/contracts/docs/framework-lifecycle
to decide what kind of change this pull request is.Checklist:
CHANGELOG.md
file in the root folder.DEPLOYMENT_CHECKLIST
file in the root folder.UPDATE_CHECKLIST
file in the root folder.