Skip to content
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

fix: Readme update #145

Merged
merged 1 commit into from
Jun 26, 2024
Merged

fix: Readme update #145

merged 1 commit into from
Jun 26, 2024

Conversation

fabriziodemaria
Copy link
Member

  • Minor fixes
  • Remove withContext and add note about using a single instance
  • Expand on the Initialization Strategy

@nicklasl
Copy link
Member

I wonder if it would make sense to have the user select an initialization strategy as part of the "sdk create function" and having the create function be suspend/async and perform the action right away?

@fabriziodemaria
Copy link
Member Author

I wonder if it would make sense to have the user select an initialization strategy as part of the "sdk create function" and having the create function be suspend/async and perform the action right away?

Yes, I think I would like that. I am especially not a fan of users having to call two functions activate and asyncFetch in succession, I'd rather manage those internally.

@fabriziodemaria fabriziodemaria merged commit 2ffc41d into main Jun 26, 2024
3 checks passed
@fabriziodemaria fabriziodemaria deleted the readme-update branch June 26, 2024 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants