quantfortune/SUP_GoldBees_Frontend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refactor strategy execution logic to improve clarity on arming conditions

Browse Source
This commit is contained in:
Thigazhezhilan J 2026-03-28 12:21:41 +05:30
parent 3640cd745e
commit 67b633ae9b
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/components/landing/PortfolioSection.tsx
View File

@ -629,8 +629,7 @@ export default function PortfolioSection() {
: "Strategy stopped";
const marketState = marketStatus?.status ?? "UNKNOWN";
const executionAllowed =
marketState === "OPEN" && (liveness === "ACTIVE" || liveness === "STOPPED");
const canArmStrategy = liveness === "ACTIVE" || liveness === "STOPPED";
const nextEligibleTs = engineStatus?.next_eligible_ts
? new Date(engineStatus.next_eligible_ts)
@ -1143,7 +1142,7 @@ export default function PortfolioSection() {
<MotionButton
{...ctaMotionProps}
onClick={handleStart}
disabled={isStarting || !executionAllowed || isStrategyActive}
disabled={isStarting || !canArmStrategy || isStrategyActive}
className="shimmer"
>
{isStarting ? "Starting..." : "Start Strategy"}