make property placeholders in xml files a bit more generic #1169
Conversation
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
|
Yay this is good. There are some new source files which needs to have the ASF license header in the top |
davsclaus
approved these changes
Aug 23, 2025
… configure different placeholder start / end tokens and customize xml namespaces they're active in
rastislavpapp
force-pushed
the
generic_placeholders
branch
from
59b0eee to
ac93147
Compare
|
added the licence headers... sorry again :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allow to configure different placeholder start / end tokens and customize xml namespaces they're active in
This enables user to configure different placeholder tokens (e.g. X{ ... } instead of ${ ... }), or different namespaces, for the XML property placeholder completion. Could solve also spring property placeholders for CE users, should they choose to configure this. (as requested in #1166)
The default configuration only includes the blueprint namespace + ${ ... } style of placeholders.
I've added a new section in the plugin config for this, looks like this:
Adding new entry:
