Skip to content

Conversation

@codingpeanut157
Copy link
Contributor

@codingpeanut157 codingpeanut157 commented Nov 21, 2025

📝 Description

it was mistakenly greied out all the times, now we have a new field in InfoReply that informs us on the status of the minting.

@codingpeanut157 codingpeanut157 self-assigned this Nov 21, 2025
@codingpeanut157 codingpeanut157 added the bug Something isn't working label Nov 21, 2025
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Nov 21, 2025

Deploying wildcat-dashboard with  Cloudflare Pages  Cloudflare Pages

Latest commit: edd936c
Status: ✅  Deploy successful!
Preview URL: https://acd73319.wildcat-dashboard.pages.dev
Branch Preview URL: https://peanut-minting-2.wildcat-dashboard.pages.dev

View logs

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes the "Enable Minting" button that was incorrectly disabled. The fix introduces a new minting_status field in the InfoReply type to properly track whether minting is enabled or disabled, replacing the previous logic that inferred minting status from keyset data.

Key changes:

  • Added MintingStatus type and minting_status field to the "Accepted" variant of InfoReply
  • Renamed newKeyset prop to mintingEnabled in the QuoteActions component for clarity
  • Updated button disabled logic to use the new minting_status field directly from the API response

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 2 comments.

File Description
src/generated/client/types.gen.ts Added MintingStatus type definition and minting_status field to InfoReply type for "Accepted" status variant
src/pages/quotes/QuotePage.tsx Renamed prop from newKeyset to mintingEnabled, updated button logic to use new API field, removed obsolete badge display, and simplified "Request to Pay" button conditional

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@codingpeanut157 codingpeanut157 force-pushed the peanut/minting_2 branch 2 times, most recently from 61e3f59 to 32b124b Compare November 21, 2025 15:44
variant={newKeyset ? "default" : "destructive"}
className={newKeyset ? "bg-red-500" : "bg-blue-500"}
variant={mintingEnabled ? "default" : "destructive"}
className={minting ? "bg-red-500" : "bg-blue-500"}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this say mintingEnabled?

Copy link

@zupzup zupzup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

className={minting ? "bg-red-500" : "bg-blue-500"}
>
{newKeyset ? "Disabled" : "Enabled"}
{mintingEnabled ? "Disabled" : "Enabled"}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this button is disabled when minting is enabled? 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes
when minting has been enabled already, the button to enable it should be disabled
😅

it was mistakenly greied out all the times, now we have a new field in
InfoReply that informs us on the status of the minting.
@codecov
Copy link

codecov bot commented Nov 21, 2025

Codecov Report

❌ Patch coverage is 0% with 8 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/pages/quotes/QuotePage.tsx 0.00% 8 Missing ⚠️

📢 Thoughts on this report? Let us know!

@codingpeanut157 codingpeanut157 merged commit f160566 into master Nov 24, 2025
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants