Conversation
barw4
added
Improvement
Ready for review
and removed
Ready for review
Bug
barw4
marked this pull request as ready for review
August 4, 2026 08:41
ibexa-workflow-automation-1
Bot
requested review from
Steveb-p,
ViniTou,
alongosz,
bnowak,
ciastektk,
konradoboza,
mikadamczyk,
tbialcz and
wiewiurdp
and removed request for
a team
August 4, 2026 08:41
konradoboza
approved these changes
Aug 4, 2026
konradoboza
left a comment
konradoboza
left a comment
Contributor
There was a problem hiding this comment.
I think it's good enough concerning avoiding BC break. Agreed that the breaking change (as in #134) will be applied on merge up to 6.0 alongside doc mention.
bnowak
approved these changes
Aug 4, 2026
|
barbaragr
approved these changes
Aug 4, 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
6 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.
Related PRs:
#124
Description:
The solution seems hacky, but a 'proper' solution is changing
locationidentifier in different areas - services, route, maybe it does make sense to do it inv6.0but I'm not sure about4.6and5.0due to BC.For QA:
Documentation: