feat: mint burn actions

[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, remove the logically unreachable or redundant part so that the condition reflects the real value domain and control flow. Here, after the if (!error) return undefined; guard, error is always non-null and non-undefined, so the || '' fallback in String(error || '') is never used.

The best minimal fix that preserves existing functionality is to replace String(error || '') with String(error) on line 24. This keeps the behavior identical for all currently possible inputs (non-nullish error), but removes the misleading conditional. No other parts of the file need to change, and no new imports or helper functions are required.

Concretely: in libs/burn-waitlist/src/lib/mint-page.tsx, inside sanitizeErrorMessage, edit the line that defines message so that it no longer uses error || ''. Everything else in the function remains as is.

In general, unused variables coming from hook destructuring should be removed from the destructuring pattern unless you intend to use them. This keeps the code clear and avoids misleading future readers into thinking the success flag is relevant to the component’s logic.

To fix this specific issue without changing functionality, we should remove isMintByAppSuccess from the object destructuring assignment that reads the result of useMintHaqqByApplication(). Since isMintByAppSuccess is not used anywhere else in the snippet, no additional changes are needed. The rest of the returned properties from the hook (mintHaqqByApplicationTx, isPending, isConfirming, hash, error) remain intact so existing behavior is unaffected.

Concretely, in libs/burn-waitlist/src/lib/waitlist-page.tsx, locate the block for “Mint HAQQ by application” (around lines 191–198). Edit the destructuring so that the isSuccess: isMintByAppSuccess, line is removed, leaving the other fields unchanged. No imports, method definitions, or other code paths need to be updated for this fix.

In general, to fix an "unused variable" warning, you either remove the variable declaration/destructuring entirely or start using the variable in a meaningful way. Since we must not change functionality and there is no indication that the transaction hash is supposed to be displayed or logged, the safest approach is to stop destructuring the unused property from the hook return value.

Concretely, in libs/burn-waitlist/src/lib/waitlist-page.tsx, in the section where useMintHaqqByApplication is called (lines ~191–198), the object destructuring currently includes hash: mintByAppHash. We should remove this hash: mintByAppHash entry from the destructuring so that the hook is still called and all other used properties (mintHaqqByApplication, isPending, isConfirming, isSuccess, error) are preserved. No additional imports or definitions are required.