Keep only async flow (suspend fun) by removing sync code

[osoykan]

No description provided.

[CanerPatir]

Hello Oğuzhan,
Sync command bus behaviors had been located to support places where don't supply async manner like Spring Boot @KafkaListener. However, we can handle sync command bus calls over Kotlin's out of the box runSync dispatcher. So It would be great enhancement @osoykan

[bilal-kilic]

I aggre this is a great suggestion to declutter the project.
Maybe we can leave sync implementations on CommandBusImpl to provide an easy way to run sync commands.

override fun <TCommand : Command> executeCommandSync(command: TCommand) = processPipeline(registry.getPipelineBehaviors(), command) {
    runBlocking {
        registry.resolveCommandHandler(command.javaClass).handle(command)
    }
}

[osoykan]

@CanerPatir 👍

@bilal-kilic The idea of removing the sync implementation is to offload the burden of the runBlocking call to the user; since Kotlin provides that functionality by nature, there is no need to keep/maintain such behavior in the codebase. So, the users can still do what you suggest in your code block.

[osoykan]

Implemented in v2.0