fix(web): appeal-tab-not-displaying-options #1298
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
subgraph needs redeployment
PR-Codex overview
Focus of the PR:
This PR focuses on adding a new
timestamp
field to theClassicDispute
entity and making changes to theuseClassicAppealContext
hook,useClassicAppealQuery
query, andStageOne
component.Detailed summary:
timestamp
field to theClassicDispute
entity insubgraph/src/entities/ClassicDispute.ts
currentLocalRoundIndex
assignment inuseClassicAppealContext.tsx
timestamp
field to theDisputeKitRound
interface insubgraph/schema.graphql
useClassicAppealQuery
query inweb/src/hooks/queries/useClassicAppealQuery.ts
isUndefined
function inweb/src/pages/Cases/CaseDetails/Appeal/Classic/Options/StageOne.tsx
StageOne
component inweb/src/pages/Cases/CaseDetails/Appeal/Classic/Options/StageOne.tsx