Coroutines based database-vertx implementation#106
Open
DmitrySadchikov wants to merge 4 commits intoTinkoff:mainfrom
Open
Coroutines based database-vertx implementation#106DmitrySadchikov wants to merge 4 commits intoTinkoff:mainfrom
DmitrySadchikov wants to merge 4 commits intoTinkoff:mainfrom
Conversation
DmitrySadchikov
force-pushed
the
database-vertx-coroutines
branch
3 times, most recently
from
fdda87f to
4a61a08
Compare
DmitrySadchikov
force-pushed
the
database-vertx-coroutines
branch
from
4a61a08 to
d2ee429
Compare
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
The implementation of the database-vertx module, which is based on Kotlin's coroutines, instead of reactor classes. Kora context is saved and obtained exclusively through CoroutineContext.
Bug fixes:
Context.Kotlin.injectmethod, kora context injection was added to CoroutineContext. Because of this bug,Context.Kotlin.currentmethod always returned a new empty context.