feat: implicit init #15
Open
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.
Overview
The SDK currently requires that
await init()
is called before class methods likeget
orcreate
can be called. Class methods run beforeinit
also return the misleading exception 'Invalid app id`Proposed changes
Run
init()
internally if not called manually. The SDK now tracks the initialized state internally and will automatically callinit()
if not initialized. This means clients no longer need toawait init()
:await init()
can still be run externally, so this is not a breaking change.Miscellaneous other fixes
private
create
,update
, anddelete
case insensitive to be consistent withget
3.2.0