Rebase befoe landing
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 6 2024
Rerbase before landing
Rebase before landing
Jun 5 2024
Make inner collection immutable. Use direct assignment in a for loop.
Fix types. Use a map of [deviceID]: IdentityPlatformDetails
Those types are totally wrong. We need mapping from device id to platform details. Interestingly reducer worked as expected - it put map into the SQLite.
- Make collection mutable.
- Use for loop instead of forEach
Make identity platform details type readonly
- Fix typing
- Use hasRun ref.
- Fix typing of MinVersionHandler
By the way, do you think it makes sense to merge this with VersionSupportedChecker component?
I was thinking about this but I couldn't find any compelling arguments against neither of those solutions. What made me finally decide to use separate component was that we have two different components to check version support on native on web. However this logic is exactly the same for both platforms so putting it inside version support checkers would result in code duplication.
Jun 4 2024
Check against usingCommServicesAccessToken before trying to sync platform details
May 27 2024
May 24 2024
Soo we will remove backupEnabledByDefault and replace it with proper check for being primary device.
rebase before landing
Rebase before landing
Rebase before landing
Rebase before landing
Rebase before landing
Rebase before landing
Rebase before landing
Rebase before landing
Rebase before landing
Rebase before landing
May 23 2024
In D12050#345321, @kamil wrote:This code (createAsyncMigrate) will be executed on app start (no matter if logged in/out). How about creating compaction after e.g. primary restore?
May 22 2024
Change & -> $