remove initializerQueue, move db logic from init to initializeApiKey,… #109
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.
… guarded db interactions with apikey check
This is part 1 of the database migration work. We need to migrate any database interaction logic in the
init
method into theinitializeApiKey
method since we will need the apiKey to interact with the database. I also run theinit
logic on thebackgroundQueue
, removing the need for a separateinitializerQueue
.Few things to note:
_dbHelper
is initialized ininitializeApiKey
now. Any public methods that interact with the database such assetUserId
,setDeviceId
,identify
, etc need to be guarded with an apiKey check to ensure[self.dbHelper]
is available[self addObservers]
toinitializeApiKey
sinceenterBackground
interacts with the DB by saving the current timestamp.