cx-composer
❯ cx-composer validate
Six layered validators surface diagnostics in the Problems panel: unknown field with did-you-mean, missing OAuth scopes, missing companion Dockerfile, unknown editorType on frontend-token-definition.json, and schema-aware batch data errors — all with red squiggles inline.
✗ client-extension.yaml:7 Unknown field "instanceableq" on customElement. Did you mean "instanceable"? ✗ client-extension.yaml:12 OAuth "my-oauth" missing required "scopes". ✗ my-theme/ Missing companion: frontend-token-definition.json. ✗ frontend-token-definition.json Token "brandPrimary": unknown editorType "Colour". Try: ColorPicker, Length, FontFamily. 4 problems found. Auto-runs on save.
06 · Validate

Catch typos before deploy fails.

Auto-runs on save/open. Six validator types: client-extension.yaml (all 28 types, did-you-mean on unknown fields), LCP.json, Dockerfile, folder-level companion checks (Dockerfile / assemble source / referenced assets), smart frontend-token-definition.json validation, and schema-aware validation for every one of 309 batch-engine entity types inside batch/*.batch-engine-data.json (Region needs countryId, TaxonomyCategory needs its parent vocabulary, etc.). Free tier covers LCP.json, Dockerfile, and yaml validation for the four static-asset CX types you iterate on most — globalJS, globalCSS, themeSpritemap, jsImportMapsEntry. Pro extends deep validation to the other 24 CX types plus folder companions, token-JSON checks, and the full 309-entity batch schema surface.

at a glance
# ────── step by step ──────

How Validate works, in 7 steps.

    01

    Auto-runs on save + open

    No command to invoke — every save re-validates every open manifest, LCP.json, Dockerfile, and batch data file.

    02

    yaml validator (28 types)

    Unknown fields flagged with did-you-mean. Missing required fields highlighted. Value completions on type:.

    03

    LCP.json + Dockerfile

    Liferay Cloud service config shape checked. Dockerfile instruction ordering + deprecation warnings flagged.

    04

    Folder-level companion checks

    Missing Dockerfile / assemble source / referenced JSON file? Diagnostic at the folder level, not just the manifest.

    05

    frontend-token-definition.json

    Walks up from the JSON to find its themeCSS block and enforces the full frontendTokenCategories → sets → tokens → mappings schema.

    06

    Batch data (309 entities)

    Schema-aware validation with 169 runtime FK patches. Catches parent-FK omissions OpenAPI misses.

    07

    Right-click to validate on demand

    Validate File on any file, or Validate Whole CX (folder) to scan an entire CX folder tree including every batch data file.