Skip to content

feat: calculator v61 redesign & os widget#554

Open
ovitrif wants to merge 2 commits into
feat/facts-v61from
feat/calculator-widget-v61
Open

feat: calculator v61 redesign & os widget#554
ovitrif wants to merge 2 commits into
feat/facts-v61from
feat/calculator-widget-v61

Conversation

@ovitrif
Copy link
Copy Markdown
Collaborator

@ovitrif ovitrif commented May 16, 2026

No description provided.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6c2d065d16

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

CalculatorHomeScreenWidgetEntryView(entry: entry)
}
.configurationDisplayName("widgets__calculator__name")
.description("widgets__calculator__description")
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Use a static calculator widget description

The home-screen widget gallery cannot perform the app's t(..., variables:) substitution here, but widgets__calculator__description is the in-app string that contains {fiatSymbol}. As a result, when users add the new Calculator OS widget from the iOS widget gallery, the description is shown with the literal {fiatSymbol} placeholder instead of a real currency symbol or generic text.

Useful? React with 👍 / 👎.

@ovitrif ovitrif marked this pull request as draft May 17, 2026 14:53
@ovitrif ovitrif changed the title feat: calculator widget v61 + OS widget feat: calculator v61 redesign & os widget May 17, 2026
@ovitrif ovitrif self-assigned this May 17, 2026
@ovitrif ovitrif added this to the 2.3.0 milestone May 17, 2026
@ovitrif ovitrif marked this pull request as ready for review May 17, 2026 17:32
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 76f4cc3403

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +103 to 105
if values.bitcoinValue.isEmpty, saved.bitcoinValue.isEmpty {
values.bitcoinValue = CalculatorWidgetValues().bitcoinValue
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve an intentionally cleared calculator amount

When the user deletes all digits from the calculator, persistValues() saves an empty bitcoinValue; on the next render this branch treats that saved empty value as uninitialized, resets it to the default 10000, and immediately persists that default again. Since load() already returns CalculatorWidgetValues() for a missing App Group value, saved.bitcoinValue.isEmpty here only represents an intentionally cleared amount, so navigating away/back or reopening the app unexpectedly changes the calculator and home-screen widget from blank/0 back to 10,000 sats.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant