-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[WIP] feat(currency): add currency display to rules #5536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for actualbudget ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
189835e
to
c96e8c9
Compare
Bundle Stats — desktop-clientHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger
Smaller
Unchanged
|
Bundle Stats — loot-coreHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller
Unchanged No assets were unchanged |
@@ -56,6 +57,7 @@ export function Input({ | |||
onChangeValue, | |||
onUpdate, | |||
className, | |||
useKeyDown = false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doing changes to the base Input
component has a very large blast radius. This addition poses significant risk. As such: it cannot be taken lightly.
Conceptually - I'm not a fan of this boolean flag that amends the existing logic. Why is this necessary? Are there other ways to achieve something similar without creating conditional logic for key up/down handling?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the feedback. I agree. This was a fast idea as the AmountInput updates the value on keyUp, but the Popover closes already on keyDown. I will have another look at it.
👋 Hi! It looks like this PR has not had any changes for a week now. Would you like someone to review this PR? If so - please remove the "[WIP]" prefix from the PR title. That will let the community know that this PR is open for a review. |
This PR was closed because it has been stalled for 5 days with no activity. |
This PR adds the currency display to the rules.
It also fixes #5476 as the AmountInput got updated to handle currency specifics.
Also it now uses the number specific InputField in the Account Filter modal:

This may break the visual of old field, but it is standardized for currency input and is already in use by the rules.
It also removes a lot of convertions like integerToAmount, amountToInteger, currencyToAmount