-
Notifications
You must be signed in to change notification settings - Fork 121
[POS as a tab i1] Cache POS tab visibility per site for initial value while checking eligibility async #15753
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
Merged
Merged
Changes from 4 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
b4edd54
Save POS eligibility to app settings per site for initial tab visibil…
jaclync 887f304
Only return cached visibility if the last check date is within 3 days…
jaclync b40a363
MainTabBarController: add a test case when POS becomes ineligible aft…
jaclync cb0a48f
Nits and remove empty spaces.
jaclync 179e629
Merge branch 'trunk' into feat/WOOMOB-611-cache-pos-eligibility
jaclync 72ff463
Replace async `AppSettingsAction` with a new `POSEligibilityService` …
jaclync 396d3a8
Remove `currentDate` and date check for initial tab visibility.
jaclync 1525029
Remove `lastPOSTabVisibilityCheckDate` from `GeneralStoreSettings`.
jaclync 80df17b
POSEligibilityServiceProtocol: rename `loadPOSTabVisibility` to `load…
jaclync 60cefb3
Nit: revert async let now that there is only one to await.
jaclync 19fdfda
Move `AppSettingsAction.setPOSTabVisibility` to `POSEligibilityServic…
jaclync f5e9709
Rename `setPOSTabVisibility` to `cachePOSTabVisibility` to better des…
jaclync f652b50
Fix trailing whitespaces.
jaclync 7b29c57
Merge branch 'trunk' into feat/WOOMOB-611-cache-pos-eligibility
jaclync File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
There's still a slight delay for the Point of Sale tab to appear.
Simulator.Screen.Recording.-.iPad.Air.13-inch.M3.-.2025-06-16.at.15.21.11.mp4
If we look at
checkInitialVisibilityimplementation, it could be synchronous, and we could call it outside theposEligibilityCheckTask, allowing for the tab to appear as soon as possible. It would require getting around dispatching AppSettingsStore and accessing the data directly, but other than that, it would allow for a smoother appearance:Simulator.Screen.Recording.-.iPad.Air.13-inch.M3.-.2025-06-16.at.15.31.22.mp4
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.
It's interesting that I didn't observe the slight delay in iOS 18.4 simulator, as in the screencast 1:06. But then I tried the same simulator type in iOS 18.5, and I see the delay now. I tried the device type as in my original screencast but in iOS 18.5 and see the same, so likely a behavior difference (probably about the timing of Task) between iOS versions. I'm looking into using a service for loading the initial visibility to make it sync.
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 suggestion, I updated the PR with a few commits to move the async initial value to a synchronous call from a new service in Yosemite
POSEligibilityServicebehind a protocol for unit testing. Also moved theAppSettingsAction/store changes to the service for consistency. Please see if the delay is fixed after the initial load when you get a chance, thanks!