Conversation
pratushnyi
approved these changes
Sep 3, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
This adds opt-in Kotlin modules without introducing Kotlin dependencies into
allure-java-commons. Kotlin users get an idiomatic top-level facade for the public Allure runtime API, including named arguments, useful defaults, unambiguous lambdas, and a Kotlin-nativeStepScope.The coroutine module adds suspend-aware steps and structured context propagation through
withAllureContext. Steps remain current across dispatcher switches, parallel child coroutines are recorded as siblings, and worker-thread context is safely isolated and restored. Failures and cancellation retain Allure’s standard status handling, while the documentation explains installation and the boundaries of annotation-based Kotlin APIs.Checklist