Skip to content

docs: clarify dynamic inline script source detection - #240

Merged
kthoms merged 2 commits into
operaton:mainfrom
pralav-25:docs/clarify-inline-script-detection
Nov 16, 2026
Merged

kthoms merged 2 commits into
operaton:mainfrom
pralav-25:docs/clarify-inline-script-detection

Conversation

@pralav-25

Copy link
Copy Markdown
Contributor

Inline scripts in languages other than JUEL are treated as dynamic source expressions when their trimmed content begins with ${ or #{. Document this rule in the scripting guide's canonical Script Source section, including the accidental-match symptom, a language-specific comment workaround, and the distinction between external resource paths and loaded file contents.

This follows the separate scripting-guide suggestion in the review of #201 and does not depend on that PR. The wording was checked against ScriptUtil, StringUtil, ScriptFactory, and ResourceExecutableScript in the engine.

Validation: npm run typecheck, npm run build, generated-page inspection, and git diff --check passed using Node 24.22.1 and the existing npm lockfile. The build reports broken-link and anchor warnings elsewhere in the documentation; this change adds no links. Tests were not added or run, per contribution instructions.

pralav-25 and others added 2 commits November 15, 2026 23:08
- placed caution box after resource-path example, where it's cleat what it qualifies
- detailed placeholder parsing for other languages
- double mentionining of leading whitespace reduced to one
@kthoms

kthoms commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

I made some editorial changes. Thanks for the proposal!

@kthoms
kthoms merged commit a4577c4 into operaton:main Nov 16, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants