---
# System prepended metadata

title: DAO Context Sync (7/19/22)

---

# DAO Context Sync (7/19/22)

- DAO overview
  - From context, being able to pull DAO overview/DAO metadat (doesn't need a filter)
- Members
  - DAO members query with the DAO address in the param and paginated to ~20 people
  - Can then pull members anywhere in the app (currently paginated to 100)
    - How would I pull *next* from the Members page -- would we use a `getNextPage` of members?
    - This would change the state in the context
  - `getNextMembers` -- pile these on to the previous list (can do an Infine Scroll or a Show More for the UX)
- Proposals
  - Have a hook for filter that adds the filter in
    - Should be able to handle any of the modifiers we'd pass in
    - Context methods that we turn into hooks

## Example Hooks

```js
const {members, filterMembers, getMoreMembers} = useMembers()
```

- These are hooks that would be exposed -- this fits with the SDK patterns pretty well
- Tradeoff is that this'll be a large Context
- How would we surface specific individual proposals?
- We'd hold all of the SDK call parameters in state and when we refresh we'd call again with the same parameters

## Questions

- What stays after a refresh?
  - Filter, sort, pagination limitations
    - Would want the same number of members that are showing
- Would there be a use case to completely reset the filters/sort/pagination limit?
  - Potentially down the road, but for now we won't include this
- Would handle route changing -- this was a pain point in the v2

## Tradeoffs

- If we do this at page level, we'd lose the overarching drag and drop context (would just be overview) but then we'd lose the query results from moving between pages
- Simple DAO context, but when we'd get to proposal list we'd need to include this data anyway