fix(frontend): restore npm run build (tsc -b) - constrain chart SeriesApi generic + onMutate return #834
No reviewers
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:implement
agent:implement
agent:open_issues
agent:ready
agent:research
agent:security_audit
agent:verify
architecture
backend
blocker:hybrid
blocker:launch
blocker:limit-orders
blocker:v2
block:log_only
block:security
bug
ci
contracts
correctness
deploy
dev
devops
docs
documentation
duplicate
e2e
enhancement
epic
feature
frontend
functional-completion
gas
good first issue
governance
help wanted
high-risk
hooks
hybrid
indexer
infra
infrastructure
integrators
invalid
launch-blocker
limit-orders
localnet
localterra
low priority
missing-implementation
needs-design
ops
performance
priority
high
priority
medium
product
qa
QA
question
ready
ready
research
scripts
security
security-hardening
smartcontracts
tech-debt
testing
ux
UX
v2
verification
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-dex-terraclassic!834
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "qa/337-build-tsc-fix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
tsc -b(run bynpm run build) was red at038a457with two type errors.vite buildalone passes (esbuild ignores types), so the production buildbreak slipped past CI, which runs vitest + eslint but not
tsc -b.Changes
priceChartLightweightSeriesSync.ts: constrainSeriesApi<T>withT extends SeriesType(matchesISeriesApi<T>).useTerraBroadcastMutation.ts: return calleronMutatecontext so react-query forwards it toonError/onSettled.Rebase / conflict resolution
Rebased onto latest
main(f875d53). Dropped accidental doc deletions that were present on the stale branch tip (unrelated #337 cross-links and Cloud Agent E2E notes indocs/testing.md).Verification checklist
cd frontend-dapp && npm run buildnpx vitest run src/components/charts/__tests__/priceChartLightweightSeriesSync.test.tsnpx vitest run src/hooks/__tests__/useTerraBroadcastMutation.test.tsx src/hooks/__tests__/useTerraBroadcastMutation.dom.test.tsxmake lint-frontendmaingit merge mainon branch tipFound via #337 PERF-00-03. Relates to #336, #305. Suggest adding
tsc -bto CI so this class of break stops recurring (same shape as #246).Security review
Commit reviewed:
6cc9e92faa64d3c89776d9f182eb5bf82346b314Scope: 2 frontend files —
priceChartLightweightSeriesSync.ts(generic constraint) anduseTerraBroadcastMutation.ts(onMutatecontext return).Outcome:
FINDINGS: 0medium+Security review: no medium+ findings on this diff.
Summary
priceChartLightweightSeriesSync.tsSeriesTypebound toSeriesApi<T>syncTimedSeriesequality checks; no new user-controlled sinks.useTerraBroadcastMutation.tsonMutatecontext to React QueryonMutate; context is app-defined, not attacker-controlled. Fix reduces risk of stale optimistic UI after failed broadcasts rather than introducing one.Checks performed
Inline threads: none (no medium+ findings).
mentioned in issue #337
changed the description
added 4 commits
PlasticDigits:mainf875d538- fix(frontend): restore `npm run build` — constrain chart SeriesApi generic + onMutate returnCompare with previous version
mentioned in commit
732a0e9b58Security review
Commit reviewed:
f875d5388a17e2467de35f7dc805ee7d77e6cea7Scope: 2 frontend files —
priceChartLightweightSeriesSync.ts(generic constraint) anduseTerraBroadcastMutation.ts(onMutatecontext return). Re-reviewed after rebase ontomain(9d3bf71).Outcome:
FINDINGS: 0medium+Security review: no medium+ findings on this diff.
Summary
priceChartLightweightSeriesSync.tsSeriesTypebound toSeriesApi<T>syncTimedSeriesequality checks; no new user-controlled sinks.useTerraBroadcastMutation.tsonMutatecontext to React QueryonMutate; context is app-defined, not attacker-controlled. Fix reduces risk of stale optimistic UI after failed broadcasts rather than introducing one.Checks performed
6cc9e92— same functional hunks after rebase; no new medium+ issues.Inline threads: none (no medium+ findings).
mentioned in commit
34af36f9bamentioned in commit
7fdd341c9c