Repository navigation
Conversation
A dot inside ${...} is Velocity property navigation, so ${db.warehouse.url}
never looks for a key of that name. Nothing says so today, and an unresolved
reference is passed through as literal text, so the failure surfaces at the
connector rather than at the key.
Adds a "Keys that contain dots" section to the Velocity page with the
${maps.get('key')} form, the priority caveat that goes with maps.get, and the
error text a reader is most likely to be searching for. Links the maps.get row
of the utility variable table to it.
Documentation only. No behaviour change.
Refs: OpenIntegrationEngine/engine#417
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: Ken Moss <46053166+djkene70@users.noreply.github.com>
jonbartels
approved these changes
Nov 6, 2026
Contributor
Author
|
Reopening to re-run the ECA check; the Eclipse account is now signed and linked. |
tonygermano
reviewed
Nov 8, 2026
tonygermano
reviewed
Nov 8, 2026
tonygermano
left a comment
Member
There was a problem hiding this comment.
I appreciate you following up here with the documentation improvement. I left an inline comment I'd like you to verify before we merge.
This is non-blocking, but you could also mention that using underscores (db_warehouse_url) or camel case (dbWarehouseUrl) can help avoid this problem.
pacmano1
approved these changes
Nov 13, 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
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.
Documentation only, no behaviour change. Follows up on OpenIntegrationEngine/engine#417, where @tonygermano pointed out that
${maps.get('key')}already reads a dotted key and asked for the documentation rather than a code change, once the wiki move had landed. It has, so here it is.What it adds
A Keys that contain dots section to
docs/engine/velocity_variable_replacement.md:.inside${...}is Velocity property navigation, so${db.warehouse.url}looks for an objectdb, not a key of that name;${maps.get('db.warehouse.url')};maps.get— it reads the first loaded map, so it returns the lowest-priority match;No suitable driver found for ${db.warehouse.url}and points at the connector rather than at the key.It also links the
${maps.get('key')}row of the utility variable table to the new section.Notes
.vitepress/config.mtsneeds no change.${...}through on purpose.🤖 Generated with Claude Code