Split qualified title paths into package segments#1284
Merged
Conversation
pratushnyi
approved these changes
Jun 11, 2026
todti
approved these changes
Jun 11, 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
3 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
Allure title paths now handle fully qualified package and class names as separate path segments instead of keeping dotted names as one combined entry. For example,
io.qameta.allureis reported asio / qameta / allure, making title-path navigation and grouping match the expected package hierarchy.The title path helper also handles null, blank, trimmed, simple, and already-qualified package/class inputs consistently, avoiding duplicated package segments and skipping empty title parts.
Checklist