Skip to content

Conversation

Dunsin-cyber
Copy link
Contributor

🚀 Summary

This pull request continues from where #3089 left off. That initial PR laid the groundwork, and this one builds upon it to complete the implementation and resolve remaining issues.

✨ Changes Introduced

A breakdown of what this PR introduces:

  • Fixed all failing tests, particularly for ConfirmPayment and SitePreferences.
  • ConfirmPayment Fix:
    Added a default mock implementation for getFormattedInCurrency in the SettingsContext. This resolves the failing unit tests in ConfirmPayment/index.test.tsx caused by a missing mock.
  • SitePreferences Fix:
    Work is still in progress for fixing the related test cases.

🔗 Related Issues or PRs

🧩 Type of Change

Select the appropriate type:

  • fix: Bug fix (non-breaking change which fixes an issue)
  • feat!: Breaking change (may break existing functionality)

📸 Screenshots (optional)

Add any relevant screenshots, screen recordings, or UI diffs to help reviewers.

🧪 How This Was Tested

  • Manual testing
  • Unit/integration tests
  • Test environment notes: [Optional: add environment or tool info if relevant]

✅ Checklist

  • Code reviewed and cleaned up
  • Manual tests run successfully
  • Automated tests added or updated
  • Documentation and guides updated (if applicable)

For UI-related changes:

  • Dark mode tested
  • Responsive layout verified

riccardobl and others added 27 commits March 16, 2024 15:36
* master: (25 commits)
  Translated using Weblate (Arabic)
  Translated using Weblate (German)
  feat: proper error messages for lndhub
  Update @getalby/sdk to version 3.6.0
  fix: use method to identify connector type
  fix: show lnaddress only for active account settings
  feat: use types
  feat: add http auth kind
  feat: fix lnaddress setting to show only to alby account
  feat: extend kind list, kind types, kind translaions
  fix: remove keys from translations
  fix: make prompt copy more clear
  feat: adapt to dynamic width of the container
  fix: account menu makeover when account name is larger
  Update i18next to version 23.11.5
  Translated using Weblate (Spanish)
  Translated using Weblate (German)
  Translated using Weblate (Portuguese (Brazil))
  fix: tests
  fix: unit tests
  ...
@Dunsin-cyber
Copy link
Contributor Author

Hi team
I optimized the input handling logic to reduce unnecessary re-renders. Initally the test recieved about 26 calls but i have optimized the input logic and reduced it to 20.

Turns out, the tests were too strict and focused more on the number and order of render-related calls rather than the actual outcome. It's working fine now, though I still plan to reduce re-renders further and optimize the test to test more on actually creating a budge rather than if the getFormattedInCurrency works well.

re-reners new number

Dunsin-cyber and others added 2 commits June 11, 2025 07:11
Currently translated at 100.0% (805 of 805 strings)

Co-authored-by: BSN ∞/21M ₿ <[email protected]>
Translate-URL: https://hosted.weblate.org/projects/getalby-lightning-browser-extension/getalby-lightning-browser-extension/de/
Translation: getAlby - lightning-browser-extension/getAlby - lightning-browser-extension
weblate and others added 8 commits June 17, 2025 20:48
Currently translated at 49.8% (401 of 805 strings)

Co-authored-by: Claudio Pastorino <[email protected]>
Translate-URL: https://hosted.weblate.org/projects/getalby-lightning-browser-extension/getalby-lightning-browser-extension/es/
Translation: getAlby - lightning-browser-extension/getAlby - lightning-browser-extension
Currently translated at 100.0% (807 of 807 strings)

Co-authored-by: BSN ∞/21M ₿ <[email protected]>
Translate-URL: https://hosted.weblate.org/projects/getalby-lightning-browser-extension/getalby-lightning-browser-extension/de/
Translation: getAlby - lightning-browser-extension/getAlby - lightning-browser-extension
@pavanjoshi914
Copy link
Contributor

this is totally messed up pr. can you please clear the commit history and make a new clean pr. its hard to review such things

@Dunsin-cyber
Copy link
Contributor Author

this is totally messed up pr. can you please clear the commit history and make a new clean pr. its hard to review such things

just to confirm, for the clean PR, would you prefer I base it off the previous contributor’s PR and include only my modifications, or should I start fresh from the main branch and re-implement both their changes and mine?

I’m happy to go either way, just want to do what’s easiest for you to review and merge.

@Dunsin-cyber
Copy link
Contributor Author

Hi, just following up on this.
should I base the clean PR on the previous one or start fresh from main?
happy to do whatever works best. 😊

just to confirm, for the clean PR, would you prefer I base it off the previous contributor’s PR and include only my modifications, or should I start fresh from the main branch and re-implement both their changes and mine?

I’m happy to go either way, just want to do what’s easiest for you to review and merge.

@pavanjoshi914
Copy link
Contributor

whichever is fine. but look at the commit history. it should be clean before the review. only the commits of based of pr and yours. i see lots of noise in this pr

@Dunsin-cyber
Copy link
Contributor Author

whichever is fine. but look at the commit history. it should be clean before the review. only the commits of based of pr and yours. i see lots of noise in this pr

oh.. alright

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.

Add unit switching within the "Amount" input

5 participants