#7 - Get the billing grace end period collection with useOnyx#84751
Conversation
|
@shubham1206agra Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button] |
|
Many of the changes are just renaming. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5bf0cfdcc8
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| snapshotReport, | ||
| snapshotPolicy, | ||
| lastPaymentMethod, | ||
| userBillingGraceEndPeriods, |
There was a problem hiding this comment.
Include billing grace periods in action callback dependencies
handleOnButtonPress now captures userBillingGraceEndPeriods but the useCallback dependency array was not updated, so when this Onyx collection arrives after initial render the callback can keep using a stale undefined value. In that state, handleActionButtonPress() may evaluate restrictions against outdated fallback data, allowing action-button flows on expense report rows to bypass the intended restricted-action redirect until another dependency happens to recreate the callback.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Hmm, why is this not caught by ESLisnt 🤔
Fixed
Codecov Report✅ Changes either increased or maintained existing code coverage, great job!
|
|
@bernhardoj Please resolve conflicts |
…ng-grace-period-subscription-utils-7
|
@shubham1206agra fixed |
|
Checking the failing typecheck |
|
Fixed |
Reviewer Checklist
Screenshots/VideosScreen.Recording.2026-03-14.at.5.37.10.PM.mov |
|
🚧 @inimaga has triggered a test Expensify/App build. You can view the workflow run here. |
|
🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
|
|
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
|
🚀 Deployed to staging by https://github.com/inimaga in version: 9.3.39-0 🚀
|
|
@bernhardoj We can't check this in app as console option is no longer available in native. Web - passed. We tried to complete 1 step in Web, than other in apps, but it doesn't work. Let me know if I missed anything. Thank you in advance Screen.Recording.20260317.235946.Expensify.mp4 |
|
🚀 Deployed to production by https://github.com/cristipaval in version: 9.3.39-3 🚀
|
Explanation of Change
Fixed Issues
$ #66456
PROPOSAL:
Tests
Same as QA Steps
Offline tests
Same as QA Steps
QA Steps
Prerequisite:
Onyx.merge('sharedNVP_private_billingGracePeriodEnd_[replaceWithYourACcountID]', {value: 1});in consolePR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectiontoggleReportand notonIconClick)src/languages/*files and using the translation methodSTYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))npm run compress-svg)Avataris modified, I verified thatAvataris working as expected in all cases)Designlabel and/or tagged@Expensify/designso the design team can review the changes.ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
web.mp4