Expand description
A language server for SFCC checkouts, answering from the checkout alone: no instance, no network.
Modules§
- api
- The
dw.*API index, generated byexamples/generate-api.rsand embedded: the checkout has no.d.ts. - cartridgepath
- Cartridge path order, which is not in the source: from editor settings, site archives or
dw.json. Settings win:dw.jsonis personal and usually ignored, and site archives are rarely checked out. - complete
- Completion:
context_atdecides where the cursor is, thenCompleterwhat to offer there. - custom
x.custom.yand preference reads, with the type ofxguessed from its name. Conservative: an unknown receiver yields nothing, an ambiguous one yields every candidate type.- diagnose
- Unknown custom attributes: SFCC returns
undefinedfor a typo rather than failing. - errors
- Pending SFCC error count from log-diff, shown via LSP progress (the only channel Zed renders for an extension).
- hover
- Route hover: who declares it, in what order, and which one a request reaches.
- isml
- The ISML tag set, so editors stop offering HTML-mode guesses like
<is:include>. - live
- The value under the cursor while debugging. Zed asks a debug adapter nothing on hover, so sfcc-dap answers on localhost.
- metadata
- Custom attributes from the metadata XML in the repository, the only local record of what
x.custom.ymay be. - reference
- resolve
- routes
- SFRA route override chains: a
replaceto the left, or a missingsuperModuleextend, silently discards handlers. - server
- sync
- Uploader state via LSP progress, Zed’s only status channel for an extension. Only uploading and failed are shown: a progress item that never ends reads as a stuck spinner.
- validate
- Form definitions and
steptypes.json: read only at run time, so typos otherwise surface in production. - workspace