Skip to content
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

fix(explorer,proposals): handle batch proposals in proposals table #6618

Merged
merged 4 commits into from
Jul 3, 2024

Conversation

edd
Copy link
Member

@edd edd commented Jun 28, 2024

  • chore(types,proposals,explorer): regenerate types switching proposals node to proposalnode
  • chore(explorer,proposals): populate all important columns with batch info
  • feat(explorer,proposals): select subproposals for the json dialog

Related issues 🔗

Closes #6555

Description ℹ️

The Proposals lib (used only in Explorer) was using a deprecated GraphQL type to select proposals. This resulted in Batch Proposals not appearing in the proposal list. This PR updates the graphQL query & handles batch proposals for the table.

Note that the Enacted column has been removed. Each proposals in a sub proposal has an individual enactment time, which makes this column not applicable. I made the decision to remove the column, because this component the enactment time is available in the JSON dialog, and most recent proposals are in batches which made this column useless. The Status column does the job of indicating if the proposal has hit its enactment period.

Demo 📺

Batches now appear in the list

Screenshot 2024-06-28 at 16 18 39

JSON view is populated with the subproposals

Screenshot 2024-06-28 at 16 19 43

valueFormatter: ({
value,
}: VegaValueFormatterParams<
ProposalListFieldsFragment,
'terms.enactmentDatetime'
'terms.closingDatetime'
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: this diff is a little misleading, I definitely didn't just change the enactment column to show closing

@edd edd marked this pull request as ready for review June 28, 2024 16:07
@edd edd requested review from a team as code owners June 28, 2024 16:07
@edd edd force-pushed the fix/6555-fix-proposal-provider branch 2 times, most recently from e42f734 to 8452187 Compare July 3, 2024 09:57
@edd edd changed the base branch from develop to next July 3, 2024 10:51
@edd edd force-pushed the fix/6555-fix-proposal-provider branch from 8452187 to 8ac1ecb Compare July 3, 2024 10:56
@edd edd merged commit cb19449 into next Jul 3, 2024
14 of 18 checks passed
@edd edd deleted the fix/6555-fix-proposal-provider branch July 3, 2024 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

proposalsDataProvider uses deprecated graphql field
1 participant