release: testedge2 waitlist

[GarageInc]

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

In general, to fix a “useless conditional” you should remove any redundant boolean checks or fallback expressions that cannot change the result given the surrounding control flow and types. Here, the earlier if (!error) guard ensures error is always truthy from that point on, so error || '' can never produce ''. We still want the behavior “if it’s an Error, use its message; otherwise convert the value to string”, but we don’t need the useless || '' for that.

The best minimal fix is to change line 44 from:

const message = error instanceof Error ? error.message : String(error || '');

to:

const message = error instanceof Error ? error.message : String(error);

This keeps the same observable behavior for all values that can actually reach this line, removes the statically useless || '', and addresses CodeQL’s complaint. No imports, new methods, or other definitions are needed, and no surrounding logic has to change. The change is confined to libs/burn-waitlist/src/lib/waitlist-page.tsx within the sanitizeErrorMessage function.

In general, when a condition is statically known to always be true or false at a given point, you should remove the conditional and keep only the branch that is actually reachable. This avoids dead code and clarifies intent.

Here, CodeQL says isConnected is always true at line 766, where we have:

{isConnected ? (
  <div> ... </div>
) : null}

To fix this without altering behavior, we should remove the ternary and just render the <div> unconditionally. Concretely:

• In libs/burn-waitlist/src/lib/waitlist-page.tsx, around lines 765–791, replace the isConnected ? (...) : null block with just the contents of the true branch (<div> ... </div>).
• No new imports, methods, or helpers are needed—this is a pure JSX/logic simplification.

To fix the problem, remove the unused Hash symbol from the import statement so that only the actually used symbols (Address, decodeFunctionData, formatUnits) remain. This keeps behavior unchanged while cleaning up the code.

Concretely, in libs/bridge/src/lib/hooks/use-withdrawal-recovery.ts, edit the import on line 5 to drop Hash from the destructuring import list. No other code changes, imports, or definitions are needed because the unused symbol is not referenced anywhere in the file.

In general, to fix an unused-import issue, remove the unused symbol from the import statement, or delete the whole import if none of its symbols are used. This reduces clutter and avoids confusion about dependencies.

Here, we should edit libs/bridge/src/lib/services/explorer-api.ts so that the import from @haqq/shell-shared only includes haqqTestethiq, which is presumably used elsewhere in the file. We will change line 7 from import { haqqEthiq, haqqTestethiq } from '@haqq/shell-shared'; to import { haqqTestethiq } from '@haqq/shell-shared';. No additional methods, imports, or definitions are required.

In general, the way to fix this type of issue is to remove the unused variable, or, if it was meant to be used, to actually consume it (for logging, UI error handling, etc.). Since we must avoid changing existing behavior, and we see no usage of currentStateError, the least invasive change is to stop declaring it.

Concretely, in libs/burn-waitlist/src/lib/hooks/use-waitlist-contract.ts, inside useWaitlistContractState, adjust the destructuring of the useReadContract return value so that it no longer includes error: currentStateError. Leave the rest of the destructured properties (data: currentState, isLoading: currentStateLoading, refetch: refetchState) unchanged, and do not add any new imports or logic. This removes the unused variable and keeps hook behavior and the component’s public API the same.

In general, to fix an unused variable from a destructuring assignment, remove the unused binding from the destructuring pattern while keeping the rest intact. This avoids changing behavior and keeps types inferred from the remaining values.

Here, in libs/burn-waitlist/src/lib/hooks/use-waitlist-contract.ts, we should edit the destructuring of useReadContract in useWaitlistContractState. Specifically, on lines 38–43, remove isLoading: currentStateLoading, from the object pattern. No other references to currentStateLoading exist, so no further changes are needed. We do not need any new imports or helper methods; the change is purely a cleanup of the destructuring.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
shell-app	Ready	Preview, Comment	Jan 23, 2026 9:33am