Skip to main content
2.3.6.8 release notes
2.3.6.8
- Updated IC for JetBrains' 2025.2 releases now that they've entered a release candidate state. As noted previously, due to breaking plugin SDK changes in 2025.2, I've had to drop IC support for 2024.*, so please make sure that you're using 2025.1 or higher. Also, due to a wholesale change to one JavaScript API, some specific types of code completions are now only available in 2025.2, particularly those for the
config
parameter of the LWC @wire
adapter. This change only affects those using IC with commercial JetBrains IDEs. - Issue 2817 - Added support for the
LightningTypeBundle
metadata type. This is another pseudo-bundle metadata type that requires specialized handling. Note that deployment errors reported against files from these bundles do not specify a valid file, so IC currently follows the Salesforce CLI's precedent of attributing those errors to the bundle's schema.json
file. Unfortunately this is rarely the actual file in which the reported error was found — it's more likely either the editor.json
or renderer.json
file — but without knowing exactly which, it's safest to guide the user to the schema.json
file that is guaranteed to be present in these bundles. - The Salesforce Code Analyzer integration no longer tries to process configuration files.
- Fixed an issue with the PMD Salesforce inspection where errors could be reported twice in markup files.