Summary
As part of the dispute-kit registry refactoring (see PR #2267), dispute kit configuration is now dynamic and works across all DisputeKits. However, several identifiers still carry a Classic-specific prefix/name that no longer reflects their generic nature.
This issue tracks the remaining workspace-level renames needed to complete the refactoring.
Scope
The following types of Classic-specific references should be reviewed and renamed where they now apply to all DisputeKits:
- Hook names (e.g.
useDisputeKitClassicMultipliers → useDisputeKitMultipliers — already done in the file, but workspace references may remain)
- React Query keys (e.g.
DisputeKitClassicMultipliers in queryKey arrays)
- File names with
Classic-specific naming that now serve all kits
- Folder names (e.g.
Appeal/Classic, Voting/Classic, Voting/Shutter) that may warrant restructuring
- Any other symbols, types, or constants prefixed with
Classic whose logic is now kit-agnostic
References
Requested by @tractorss.
Summary
As part of the dispute-kit registry refactoring (see PR #2267), dispute kit configuration is now dynamic and works across all DisputeKits. However, several identifiers still carry a
Classic-specific prefix/name that no longer reflects their generic nature.This issue tracks the remaining workspace-level renames needed to complete the refactoring.
Scope
The following types of
Classic-specific references should be reviewed and renamed where they now apply to all DisputeKits:useDisputeKitClassicMultipliers→useDisputeKitMultipliers— already done in the file, but workspace references may remain)DisputeKitClassicMultipliersinqueryKeyarrays)Classic-specific naming that now serve all kitsAppeal/Classic,Voting/Classic,Voting/Shutter) that may warrant restructuringClassicwhose logic is now kit-agnosticReferences
Requested by @tractorss.