Remove customKeypad from input-number props#3547
Conversation
…` option for the input-number widget has been removed. Callers should continue to use `apiOptions.customKeypad` instead.
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.
Tip: disable this comment in your organization's Code Review settings.
🗄️ Schema Change: Changes Detected
|
🛠️ Item Splitting: Changes Detected
|
|
Size Change: -18 B (0%) Total Size: 502 kB 📦 View Changed
ℹ️ View Unchanged
|
npm Snapshot: PublishedGood news!! We've packaged up the latest commit from this PR (885e4a8) and published it to npm. You Example: pnpm add @khanacademy/perseus@PR3547If you are working in Khan Academy's frontend, you can run the below command. ./dev/tools/bump_perseus_version.ts -t PR3547If you are working in Khan Academy's webapp, you can run the below command. ./dev/tools/bump_perseus_version.js -t PR3547 |
Summary:
This prop wasn't used. The input-number widget uses
apiOptions.customKeypadinstead.
Issue: none
Test plan:
CI checks should pass.