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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Namespace prefix support #1792
base: main
Are you sure you want to change the base?
Namespace prefix support #1792
Changes from 25 commits
532b891
be3dbad
2894b9b
dcb611b
2bf73c4
a059e62
b3e388f
daed38b
52afd07
32d0c34
2717a99
35d65b3
0a0ed06
a4fa993
57a23fc
016e232
6a32fa9
e36fb7b
011babd
1fd4024
0d39103
9f2afd2
1295f12
91e5a57
302dd5f
e002c6a
24482ee
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the current form a keyexpr is transformed from
a/b/c
to@foo/prefix/a/b/c
.Would it make sense to simply invert the order to
a/b/c/@foo/prefix
?Would it make the whole namespace prefix logic simpler?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I understand the comment, In this PR it is indeed supposed to be transformed into
a/b/c/@foo/prefix
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the clarification. I see the intended behaviour was introduced by #1780 and integrated in this PR. I was momentarily misled by this PR title.