IDE extensionIDE extensiontypeInstalls into a development environment (VS Code, Eclipse with ABAP Development Tools, SAP Business Application Studio) and works inside it, rather than as a library you call or a command you run.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

cds-intellij

SAP CDS language support for IntelliJ IDEA.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Provides
Editor supportCAPEditor supportcapabilityWorking in source code with the editor helping rather than treating it as text — completion, go-to-definition, inline errors, refactoring and preview.

Who is behind it

SAP Cloud Application Programming ModelSAP Cloud Application Programming ModelOrganisationMaintains this
In the atlas: maintains 34
@cap-js
maintainerAjinkya PatilPersonContributes to this
In the atlas: contributes to 112
@ajinkyapatil8190
Christian GeorgiPersonContributes to this
In the atlas: maintains 1, contributes to 53
@chgeo
Christian FuchsPersonContributes to this
In the atlas: contributes to 3
@manwithafox
René JeglinskyPersonContributes to this
In the atlas: contributes to 20
@renejeglinsky
Tim Schulze-HartungPersonContributes to this
In the atlas: contributes to 4
@tim-sh
5 contributors

What it declares

Every artifact

Type
IDE extension
Origin
By SAP

As an IDE extension

Installs into
IntelliJ IDEA
Distributed through
JetBrains Marketplace

Connections1

README

quoted from cap-js/cds-intellij under Apache-2.0, read
cap-js/cds-intellij/README.mdOn GitHub

SAP CDS Language Support for IntelliJ IntelliJ

SAP CDS Language Support for IntelliJ

REUSE status Main build passing Release build passing IntelliJ Version

Description

Welcome to SAP CDS Language Support for IntelliJ. It is a plugin for IntelliJ IDEs that provides editing and development support for the CDS language as used in the SAP Cloud Application Programming Model (CAP).

Features

Look at our comprehensive list of features.

Code Completion

Requirements

Supported IDEs

This plugin is compatible with a variety of IntelliJ IDEs, paid and community editions, including IDEA and WebStorm. Check https://www.jetbrains.com/ to find out which option is best for you.

Operating Systems

Tested on Windows, macOS, and Linux.

Download and Installation

Prepare your environment:

  1. Install required Node.js version on your computer if not already present.
  2. Register the new Node.js installation in your IntelliJ IDE by going to File > Settings > Languages & Frameworks > CDS.
  3. If you have installed the SAP CDS Language Support for IntelliJ plugin from a ZIP file before, uninstall it.
    • Note: we have reset the current plugin version to 1.0.0 for the first JetBrains Marketplace release, to clarify that the feature set is still incomplete.

Install or update the plugin:

  1. In your IntelliJ IDE, go to File > Settings > Plugins.
  2. Click the Marketplace tab.
  3. Search for "SAP CDS Language Support" and click Install.

Note: Support for Community editions of IntelliJ IDEs is currently in beta stage and requires manual installation from GitHub. Tap Shift twice, then select Install Plugin from Disk...

How to Obtain Support

Create an issue in this repository if you find a bug or have questions about the content.

For additional support, ask a question in SAP Community.

Terms
  • Language servers: provide language-specific features like code completion, diagnostics, etc.
  • Language Server Protocol (LSP): common protocol for communication between IDEs and language servers.

SAP CDS Language Support for IntelliJ is based on the following components:

ComponentRolePublisher
CDS Language Server (cds-lsp, running on Node.js)SAP CDS Language SupportSAP
CDS TextMate bundleCDS syntax highlighting(shipped with cds-lsp)
LSP4IJ pluginLSP support in IntelliJRed Hat
Known Compatibility Issues
SymptomSolution
SAP CDS Language Support for IntelliJ is not enabled in the IDE.1.x versions of the plugin are not compatible with the free IntelliJ Community Edition. Make sure you are using a version ≥ 2.x of the plugin.
CDS file icons are missing and/or no syntax highlightingUninstall any previous versions of the plugin (File > Settings > Plugins). Remove the 'cds' TextMate Bundle (File > Settings > Editor > TextMate Bundles). Restart the IDE. Install the latest plugin version.
Logs

To aid support, please include relevant log files in your report. Depending on the kind of problem encountered, you may want to include the logs from the IDE, the LSP4IJ plugin, the CDS Language Support Plugin, the LSP client–server (stdio) communication, and/or the LSP server.

IDE Logs

Logs produced by the IDE can be found by opening the Help menu and selecting Show Log in . See Locating IDE log files for more information.

LSP4IJ Plugin Logs and Stdio Communication

To include any errors occurring in the LSP4IJ Plugin in the IDE logs, click View > Tool Windows > Language Servers. Click on CDS Language Server. On the right-hand side, open the Debug tab on the right and select Error reporting: In log. After selecting Trace: Verbose, you'll find the stdio communication after clicking on the language-server instance (below 'CDS Language Server' on the left) and opening the Traces tab on the right.

CDS Language Support Plugin Logs

To include debug logs produced by the SAP CDS Language Support for IntelliJ plugin, you need to enable the corresponding settings in the IDE:

  • Open the Help menu and select Diagnostic Tools > Debug Log Settings….
  • In the dialog that opens, add the following lines (omit sub-categories if not needed):
cds-intellij
cds-intellij/TextMate Bundle
cds-intellij/Code Style
cds-intellij/Language Server
  • Click OK to save the settings.
Plugin Debug Mode

To enable further logging and debugging, enable plugin debug mode by setting the following environment variable for your IDE by modifying your IDE's vmoptions file:

  • Edit the file specific to your IntelliJ installation by opening the IDE and going to Help > Edit Custom VM Options....
  • Add the following line:
-DDEBUG=cds-lsp

Alternatively, set the following environment variable for your IDE:

DEBUG=cds-lsp

Restart the IDE to apply the changes.

This setting will enable:

  • tracing for the LSP server (see below),
  • Node.js debugging for the LSP server, allowing you to attach a debugger.
Stdio Logs

Open the stdio logs by going to View > Tool Windows > Language Servers, selecting the CDS Language Server, and viewing the Traces tab.

Alternatively, find the log file in the plugin directory, at lib/cds-lsp/stdio.json.

LSP Server Logs and Tracing

Open the LSP server logs by going to Help > Find Action > CDS > LSP Server Logs > Show Log File in your IDE. Alternatively, copy the file path by going to Tools > CDS > LSP Server Logs > Copy Log File Path.

The log file will be located:

  • in your system temporary directory, sub-folder cdxlsp, by default;
  • in a subfolder .cds-lsp of your project, if that subfolder contains a .settings.json file.
Trace Level

LSP-server tracing is set to level verbose by default in plugin debug mode.

To change verbosity, add the setting CDS_LSP_TRACE_COMPONENTS=*:debug to the environment variables for the LSP server by going to File > Settings > Languages & Frameworks > CDS in your IDE and adding it to the Additional env for LSP server field (separate multiple env variables with a semicolon). Restart the IDE to apply the changes.

Available trace levels are infrastructure, error, warning, info, verbose, and debug (ascending verbosity). To disable tracing, set CDS_LSP_TRACE_COMPONENTS= (empty value).

Note that for large projects, more verbose tracing may significantly inflate logs and negatively impact performance. Use it with care.

Contributing

If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.

Telemetry and Data Collection

This plugin collects usage data to help improve SAP products and enhance the user experience. The collected data is sent to SAP in accordance with our Privacy Statement.

If you prefer not to share usage data, you can disable telemetry by setting sapbas.telemetryEnabled to false in your IDE settings: File > Settings > Languages & Frameworks > CDS > Language Server (section "Telemetry").

License

Copyright (c) 2024 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.

Copyright © 2024 JetBrains s.r.o. IntelliJ IDEA and the IntelliJ IDEA logo are registered trademarks of JetBrains s.r.o.

Apache-2.0, read

History

Latest

v3.1.1

Notes

Build 56

Fixed
  • Guard blank Node.js interpreter before starting the language server

For details see the <a href=&https://github.com/cap-js/cds-intellij/compare/3.1.0...3.1.1&>full changelog

  1. v3.1.0

    Notes

    Build 55

    Changed
    • Upgrade @sap/cds-lsp from 10.0.1 to 10.1.1 with the following additions and changes:
      • Formatting: new option maxAlignmentWhitespace to disable an alignment that would leave more than the configured number of blanks before any of its members, counting the mandatory separating blank
      • User setting to compile as many model files as possible in one compilation. To enable set cds.workspace.compileFilesSeparately to false. This will boost performance for many larger models. In case duplicate definition diagnostics appear check the files involved, and in case some files should not be picked up, add the glob patterns to cds.workspace.additionalIgnorePatterns (as workspace setting).
      • Important: minimum required NodeJS version is now 24.16.0
      • Fixed: Syntax highlighting: delimited and quoted identifiers in using, namespace, context and extend
      • Fixed: Syntax highlighting: multiple ;-separated elements or enum values on a single line
      • Fixed: Syntax highlighting: first segment of a qualified type path (Foo:bar)
      • Fixed: cds-typer settings containing spaces no longer break the language server on Windows
      • Fixed: Formatting: no longer inserts whitespace after the colon of a colon-prefixed variable (e.g. :config) when aligning expressions and conditions
      • Fixed: support for CDS files with >65k lines
      • Fixed: JSON configs with null values
      • Fixed: indexing of CSN files
    • Upgrade LSP4IJ to 0.21.0, fixing compatibility with IntelliJ 2026.2 and reducing IDE freezes and errors

    For details see the <a href=&https://github.com/cap-js/cds-intellij/compare/3.0.1...3.1.0&>full changelog

  2. v3.0.1

    Notes

    Build 54

    Changed
    • Upgrade @sap/cds-lsp from 9.8.0 to 10.0.1 with the following additions and changes:
      • Formatting: new option annotationInNewLine to start elements on a new line after their annotation in annotate blocks
      • Formatting: new option asProjectionInNewLine to start as projection on / as select from in a new line (indented)
      • Formatting: new option conditionInNewLine to put ON conditions on a separate line
      • WorkspaceSymbols: also include models defined in build tasks
      • index persistency is enabled by default, can be switched off via user setting cds.workspace.persistency.enabled
      • Fixed: Formatting: align post-annotations (e.g. @mandatory) in parameter lists
      • Fixed: Formatting: align virtual and element keyword modifiers with element name if alignAfterKey is set
      • Fixed: Support lookup dirs defined in subfolders e.g. pom.xml (resolve cds env per project root instead of workspace root)
      • Fixed: WorkspaceSymbols: NodeJS V8 crashed for very large workspaces
      • Fixed: WorkspaceSymbols: filter out symbols from ignored files
      • Fixed: Add quotes around the binary in the default cds-typer command to support paths with non-alphanumeric characters
    • Upgrade LSP4IJ to 0.20.1, fixing memory leaks, editor-thread (EDT) errors, and code-action consistency

    For details see the <a href=https://github.com/cap-js/cds-intellij/compare/2.3.1...3.0.0>full changelog

  3. v3.0.0

    Notes

    Build 53

    Changed
    • Upgrade @sap/cds-lsp from 9.8.0 to 10.0.1 with the following additions and changes:
      • Formatting: new option annotationInNewLine to start elements on a new line after their annotation in annotate blocks
      • Formatting: new option asProjectionInNewLine to start as projection on / as select from in a new line (indented)
      • Formatting: new option conditionInNewLine to put ON conditions on a separate line
      • WorkspaceSymbols: also include models defined in build tasks
      • index persistency is enabled by default, can be switched off via user setting cds.workspace.persistency.enabled
      • Fixed: Formatting: align post-annotations (e.g. @mandatory) in parameter lists
      • Fixed: Formatting: align virtual and element keyword modifiers with element name if alignAfterKey is set
      • Fixed: Support lookup dirs defined in subfolders e.g. pom.xml (resolve cds env per project root instead of workspace root)
      • Fixed: WorkspaceSymbols: NodeJS V8 crashed for very large workspaces
      • Fixed: WorkspaceSymbols: filter out symbols from ignored files
      • Fixed: Add quotes around the binary in the default cds-typer command to support paths with non-alphanumeric characters
    • Upgrade LSP4IJ to 0.20.1, fixing memory leaks, editor-thread (EDT) errors, and code-action consistency

    For details see the <a href=https://github.com/cap-js/cds-intellij/compare/2.3.1...3.0.0>full changelog

  4. v2.3.1

    Notes

    Build 51

    Changed
    • Upgrade @sap/cds-lsp from 9.7.0 to 9.8.0 with the following additions and changes:
      • Fixed: Running CDS Typer in WSL projects
      • Fixed: Indentation of annotations to entities with annotated actions

    For details see the <a href=https://github.com/cap-js/cds-intellij/compare/2.3.0...2.3.1>full changelog

  5. v2.3.0

    Notes

    Build 50

    Added
    • Add setting to disable on-type formatting
    Fixed
    • Add viewBox attribute to repair SVG icons
    • Declaratively enable TextMate bundle and remove legacy entries
    • Use client-side on-type formatting

    For details see the <a href=https://github.com/cap-js/cds-intellij/compare/2.2.0...2.3.0>full changelog

  6. v2.2.0

    Notes

    Build 49

    Changed
    • Renewed user-settings page in line with the VSCode extension
    • Upgrade @sap/cds-lsp from 9.6.2 to 9.7.0 with the following additions and changes:
      • Support for multi-cursor range expansion/shrinking
      • Support folding ranges, especially for consecutive statements
      • JSON schema for user settings
      • Progress reporting for persistency operations
      • Disable type generation for current session when preconditions not fulfilled after first try
      • Fixed: Formatter: align element names after keyword only

    For details see the <a href=https://github.com/cap-js/cds-intellij/compare/2.1.0...2.2.0>full changelog

  7. v2.1.0

    Notes

    Build 48

    Added
    • Enable telemetry by default (disabled via user setting sapbas.telemetryEnabled)
    Changed
    • Upgrade LSP4IJ to 0.19.1, fixing CDS language support in WSL workspaces and tab-size configuration
    • Upgrade cds-lsp to 9.6.2 with the following changes since 9.4.0:
      • Telemetry support independent from client
      • Fixed syntax highlighting in bracketed expressions and annotate statements with constraints containing function calls
      • *.json files are no longer scanned and parsed heuristically if they contain CSN. Those files need to be used from a CDS file to be seen e.g. in Workspace Symbols. However, files ending with .csn.json or .csn are still considered as CSN files.
      • Removed user setting cds.workspace.debounceFastChanges, now always enabled
      • (Experimental) persistency of where-used index (enabled via user setting cds.workspace.persistency.enabled with more fine-tuning settings available)
      • Compatibility with @sap/cds 9.5
    • Update cds-lsp user settings and defaults, improve UX
    Fixed
    • Always use configured/default CDS tabSize
    • Resolve race condition in language-server startup

    For details see the <a href=https://github.com/cap-js/cds-intellij/compare/2.0.1...2.1.0>full changelog

  8. v2.0.1

    Notes

    Build 46

    Changed
    • Important: minimum required Node.js version is now 22.15.1
    • Include @sap/cds-lsp 9.4.0 with the following changes since 9.2.1:
      • fix: Code completion for annotations:
        • In certain cases proposals added a superfluous &@& character
        • Entries in annotation expressions could be shown twice
        • SQL functions could have been suggested in annotation expressions
      • fix: Element names are now correctly highlighted even without type specification
      • Remove temporary user setting &cds.workspace.fastDiagnosticsMode&. The default so far &clear& is now the only mode.
    • Upgrade LSP4IJ to 0.17.0, fixing Workspace Symbols
    Fixed
    • Exclude .json files from being handled by CDS LSP server

  9. v2.0.0

    Notes

    Build 45

    Added

    • Support for Community Editions of IntelliJ IDEs
      (The plugin is now based on the LSP4IJ plugin, which therefore gets installed in addition.)
    • IDE features unlocked via LSP4IJ 0.14.2:
      • Go to Declaration and Implementation (navigate to symbol declarations and implementations)
      • Highlight Usages in File (highlights symbol usages)
      • Structure Tool Window (populates and updates the file structure panel)
      • Go to Symbol (find/list symbols in workspace)
      • On-the-fly Code Formatting (format block when finishing it with } or ;)
      • Format Selected Code (range formatting)
    • Plugin settings:
      • User settings for language server
      • Node.js interpreter path (to modify result of automatic search)
      • Additional environment variables for CDS Language Server
    • Intention to convert HTTP files to IntelliJ-compatible format (useful for .http files created with cds add http)
    • Code-Style setting to put multiple parenthesized arguments or filters on a new line
    • Actions to open or copy the paths of the log files for LSP stdio and server tracing, respectively
    Changed
    • Search suitable Node.js interpreter on first start of plugin
    • include @sap/cds-lsp 9.2.1 with the following changes since 9.1.0:
      • Formatting:
        • Added options `whitespaceBeforeColonInParamList` and `whitespaceAfterColonInParamList` to control whitespace around colons in parameter lists
        • fix: Colons in type paths are no longer aligned with other colons, nor are they padded with spaces
      • Maximum log-file size can now be increased to at most 1 GB (default limit unchanged at 10 MB)
      • Performance optimizations when updating dependency net of CDS file dependencies
      • fix: Using paths which end with a folder name were not resolved correctly
      • fix: Formatter support for == operator
      • fix: Goto implementation for NodeJS services, entities, events, actions and functions, services and entities for Java
    • Automatically fix invalid Node.js interpreter path in settings on plugin start or when opening settings
    Fixed
    • Correctly validate Node.js interpreter path when opening settings
  10. v2.0.0-rc4

    Notes

    Build 43

    Changes since version 1.6.0

    Added
    • Support for Community Editions of IntelliJ IDEs
      (The plugin is now based on the LSP4IJ plugin, which therefore gets installed in addition.)
    • IDE features unlocked via LSP4IJ 0.14.2:
      • Highlight Usages in File (highlights symbol usages)
      • Structure Tool Window (populates and updates the file structure panel)
      • Go to Symbol (find/list symbols in workspace)
      • On-the-fly Code Formatting (format block when finishing it with } or ;)
      • Format Selected Code
    • User settings:
      • Node.js interpreter path (to modify result of automatic search)
      • Additional environment variables for CDS Language Server
    • Code-Style setting to put multiple parenthesized arguments or filters on a new line
    Changed
    • Search suitable Node.js interpreter on first start of plugin

  11. v2.0.0-rc3

    Notes

    Build 42

    Changes since version 1.6.0

    Added
    • Support for Community Editions of IntelliJ IDEs
      (The plugin is now based on the LSP4IJ plugin, which therefore gets installed in addition.)
    • IDE features unlocked via LSP4IJ 0.14.2:
      • Highlight Usages in File (highlights symbol usages)
      • Structure Tool Window (populates and updates the file structure panel)
      • Go to Symbol (find/list symbols in workspace)
      • On-the-fly Code Formatting (format block when finishing it with } or ;)
      • Format Selected Code
    • User settings:
      • Node.js interpreter path (to modify result of automatic search)
      • Additional environment variables for CDS Language Server
    Changed
    • Search suitable Node.js interpreter on first start of plugin

  12. v2.0.0-rc2

    Notes

    Build 40

    Changes since version 1.6.0

    Added
    • Support for Community Editions of IntelliJ IDEs
      (The plugin is now based on the LSP4IJ plugin, which therefore gets installed in addition.)
    • IDE features unlocked via LSP4IJ 0.14.2:
      • Highlight Usages in File (highlights symbol usages)
      • Structure Tool Window (populates and updates the file structure panel)
      • Go to Symbol (find/list symbols in workspace)
      • On-the-fly Code Formatting (format block when finishing it with } or ;)
      • Format Selected Code
    • User settings:
      • Node.js interpreter path (to modify result of automatic search)
      • Additional environment variables for CDS Language Server
    Changed
    • Search suitable Node.js interpreter on first start of plugin
  13. v1.6.0

    Notes

    Build 39

    Changed

    • Include @sap/cds-lsp 9.1.0 with the following changes since 8.9.1:
      • Support Node.js 24
      • Performance/Responsiveness:
        • Reduce "lagging red underline" while typing - configurable via user setting `cds.workspace.fastDiagnosticsMode`
        • Outdated compilations in background are aborted fast. This increases responsiveness and reduces CPU usage and is especially useful for large projects with many files.
      • Hovering over errors shown explanation for many error types
      • Hovering over built-in types shows documentation
      • Formatter: New option `boolOpsAtLineEnd` to position `and`, `or` operators at line end
      • Formatter: New option `argsInNewLine` to put multiple arguments to e.g. function calls on a new line
      • Formatter: Chained method-like function calls are now broken into separate lines
      • Formatter: More compact formatting of `case` statements
      • Formatter fixes:
        • Original empty lines are now correctly preserved before single-lined blocks
        • Separate alignment of annotations before resp. within projection-like entities
        • Separate alignment of annotations to entity and select items
        • Highlighting of parenthesized annotations with strings containing a colon
        • Highlighting of comments in queries
  14. v2.0.0-rc1

    Notes

    Build 36

    Changed

    • Remove upper version limit for IDE platform
    • include @sap/cds-lsp 9.0.1 with the following changes since 8.9.0:
      • Add support for Node.js 24
      • Add formatting option `boolOpsAtLineEnd` to position `and`, `or` operators at line end
      • Hovering over errors shows explanation for many error types
      • Hovering over built-in types shows documentation
      • Where-used functionality now based on new index
      • More compact formatting of `case` statements
      • Fix separate alignment of annotations to entity and select items
      • Fix highlighting of parenthesized annotations with strings containing a colon
      • Fix highlighting of comments in queries
      • Fix formatting of annotations in parentheses with values containing spaces
    Fixed
    • via LSP4IJ 0.14.0:
      • Various bug fixes
      • Performance and stability improvements
  15. v1.5.0

    Notes

    Build 34

    • Compatibility with platform 2025.1
    • Include @sap/cds-lsp 8.9.1 with the following changes since 8.5.1:
      • minimum required NodeJS version is now 20.15.1
      • fixed formatting of annotations in parentheses with values containing spaces
      • fixed auto-update of Annotation Modeler plugin
      • fixed Document highlights which sometimes showed wrong ranges for namespaces
      • use new CDS parser

  16. v2.0.0-beta2

    Notes

    Build 30

    • Consuming @sap/cds-lsp 8.9.0
    • Consuming LSP4IJ 0.12.0 (which fixes some IDE freezes among others)

  17. v1.4.2

    Notes

    Build 24

    • Create .cdsprettier.json only for CDS projects, determined by a .cds file being opened. This applies to the events of project create, project open, and settings confirmation.

  18. v1.4.1

    Notes

    Build 23

    • Only formatting settings differing from the default or previously contained in .cdsprettier.json are now stored in that file.
    Fixed
    • The TextMate bundle for syntax highlighting is now correctly unregistered when the plugin is disabled or uninstalled.

  19. v1.4.0

    Notes

    Build 22

    • CDS Formatting Options can now be configured under Settings > Editor > Code Style > CDS.
      • A .cdsprettier.json file in the project root is kept in sync with the options for consumption by the cds-lsp server.
      • Options depending on a switched-off option are disabled.
    Changed
    • include @sap/cds-lsp 8.5.1 with the following changes since 8.4.3:
      • enabling newParser via cds.env will no longer interfere with language server
      • improved telemetry messages
      • With @sap/cds 8.5.0 one of the default locations for translation folders (assets/i18n) was removed

    Note: Re-release to remove usage of an internal API.

  20. v1.3.0

    Notes

    Build 19

    • Determine suitable Node.js runtime automatically (no need to modify PATH environment variable anymore).
    Changed
    • include @sap/cds-lsp 8.4.3 with the following changes since 8.3.2:
      • fix: highlighting of escaped identifiers and parameter lists
      • fix: using path proposals could have been suggesting JS files instead of CDS files in certain cases
      • fix: on Windows if client mixes upper- and lowercase drive letters some requests could have failed
      • fix: CDS Typer was called when deleting a file which led to a misleading error output
      • minimum required NodeJS version is now (back to) 20.9.0

  21. v1.2.0

    Notes

    Build 18

    • include @sap/cds-lsp 8.3.2 with:
      • support for annotation modeler to remove certain code completions from compiler in favor of more suitable ones
      • show absolute name and kind of artifact in hover and completion details
      • analyze-dependencies command now supports rendering to svg or json string
      • fix: highlighting of CASE-statement keywords when put in their own line
      • fix: analysis of dependencies for certain cases

  22. v1.1.1

    Notes

    Build 16

    • Specify platform 2024.3 as highest compatible version

  23. v1.1.0

    Notes

    Build 14

    • include @sap/cds-lsp 8.2.1 with:
      • code completion for artifacts within using statements now also completes single name segments with complete name
      • minimum required Node.js version is now 20.9.0
      • hover and completion proposal details now show artifact kind
      • fix: highlighting of element names in annotate statements and of special element names entity, type, event
      • fix: completion: rename of source folders led to wrong using path proposals
      • fix: completion: using path proposals did not work in multi-line using statements
      • fix: maintain translation quickfix sent wrong document version

  24. v1.0.0

    Notes

    Build 13

    • Support Find References
Editor support
  1. abap-adt-apiJS/TS client for the ADT resources of an ABAP systemfrom ABAP
  2. abap2UI5 PlaygroundIn-browser ABAP editor beside the abap2UI5 app it buildsfrom ABAP
  3. abap2UI5 for VS CodeVS Code extension to preview, activate and lint abap2UI5 appsfrom ABAP
  4. vscode-tabl-ddicVS Code syntax highlighting for .tabl.ddic table definitionsfrom ABAP
  5. HammerNative macOS code editor for ABAP and CDSfrom ABAP
  6. cds-eclipse-pluginEclipse plugin for the CDS languagefrom CAP
  7. @arc-mcp/adt-lsTypeScript SDK over SAP's headless adt-ls language serverfrom ABAP
  8. abapthemesThree colour themes for ABAP source in ADT for Eclipsefrom ABAP
  9. SAP Build CodeDevelopment environment on BTP for UI5, Fiori, mobile and CAPfrom BTP/BAIP
  10. SAP Business Application StudioBrowser-based development environment with dev spacesfrom BTP/BAIP
  11. SAP Web IDE Full-StackIDE service on SAP BTP for SAPUI5, Fiori and full-stack appsfrom BTP/BAIP
  12. Cloud ALM Link for ADTEclipse plugin linking ABAP transports to SAP Cloud ALM featuresfrom ABAP
  13. ABAP Call HierarchyEclipse plugin showing the call hierarchy of ABAP membersfrom ABAP
  14. abap-call-hierarchyADT backend for the ABAP Call Hierarchy Eclipse pluginfrom ABAP
  15. abap-tags-backendADT backend for the ABAP Tags Eclipse pluginfrom ABAP
  16. ABAP TagsEclipse plugin for tagging ABAP repository objectsfrom ABAP
  17. BellaEclipse plugin bringing Claude into ABAP Development Toolsfrom ABAP
  18. ABAP Syntax HighlightingVS Code syntax highlighting for .abap filesfrom ABAP
  19. abapfs_extensionsABAP objects enabling ADT updates on systems older than 7.51from ABAP
  20. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystemfrom ABAP
  21. ABAP Development Tools for EclipseSAP's Eclipse plugins for ABAP development over ADTfrom ABAP
  22. ABAP Development Tools for VS CodeSAP's ABAP tools in VS Code for editing, debugging, ATC and transportsfrom ABAP
  23. @sap/cds-lspLanguage server for CDSfrom CAP
  24. cds-textmate-grammarTextMate grammar for the CDS languagefrom CAP
  25. @sap/ux-cds-odata-language-server-extensionOData annotation features for the @sap/vscode-cds extensionfrom CAP
  26. @sap/vscode-cdsCDS language support for VS Code and Business Application Studiofrom CAP
  27. vscode-ui5-language-assistantVS Code extension for SAPUI5 and OpenUI5 XML views and manifestfrom UI5
  28. @saptools/hana-lensWorkspace-wide CSN cache for querying CAP entities and columnsfrom CAP
  29. @saptools/sqltoolsSQLTools connection from a Cloud Foundry app's HANA bindingfrom BTP/BAIP
  30. zed-cds-extensionCDS language support for the Zed editorfrom CAP
  31. my-ide-actionsCollection of ABAP Development Tools IDE Actionsfrom ABAP

Details

Sources3
GitHub APIdiscovered herechecked
github.com/cap-js/cds-intellijtree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaGitHub API
first seen in the atlas
ecosystem and domaincap, developer-experience
Contributors5

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:cap-js-cds-intellij
JSON
/artifacts/cap-js-cds-intellij.json
MCP
Connecting an agent