Files
computer-playbook/docs/contributing/artefact/files/role/javascript.js.md
T
Environment TestandClaude Sonnet 4.6 0b8e16a45d test(lint): add markdown link checker and fix all broken links
Add tests/lint/repository/test_markdown_links.py — a hard-fail lint
test that scans all git-tracked markdown files for broken relative and
repo-root-absolute links. Skips external URLs, anchor-only links, fenced
code blocks, and placeholder targets.

Apply documentation.md rules to all staged files: add emojis after
headlines in docs files, remove emojis from role README headings,
standardize Credits sections to the canonical format, remove empty
sections and orphaned sentences referring to missing documentation files,
fix raw URLs and incorrect link text across role READMEs and docs.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-10 22:00:46 +02:00

2.0 KiB

javascript.js 📜

This page is the SPOT for role-local JavaScript injection and browser-side integration behavior. Use this page for injector wiring, activation, and repository-wide behavior rules. For implementation scope, DOM strategy, and live review, see Agent javascript.js. For browser-side validation requirements after visible behavior changes, see Playwright Tests.

javascript.js.j2 ⚙️

  • sys-front-inj-javascript loads templates/javascript.js.j2 when it exists and otherwise falls back to files/javascript.js.
  • The injector runs when compose.services.javascript.enabled is enabled.
  • The loaded script is collapsed into a one-liner before injection and added to the CSP hash list so inline execution remains consistent with the generated policy.
  • You MUST use javascript.js.j2 when the script depends on role variables or inventory values, and use files/javascript.js when the script is static.

Inventory 📋

  • You MUST keep compose.services.javascript.enabled enabled in the role configuration or override it in the inventory when JavaScript injection should run.
  • You MUST pass only the runtime values that the browser logic actually needs. Keep the rendered template surface small and explicit.

Repository Rules 📏

  • You MUST use role-local JavaScript only for browser-side integration gaps that cannot be solved cleanly through app configuration or CSS alone.
  • When OIDC is enabled, you MUST disable or hide the normal login form in the UI if the target application does not already provide a dedicated configuration switch for that behavior.
  • You MUST disable UI fields that are authored by OIDC or LDAP so users do not edit values locally that are managed by the identity provider or directory.
  • You MUST NOT write values back from those UI fields to OIDC or LDAP through injected JavaScript. Treat those fields as externally managed and read-only in the application UI.