Post date: October 21, 2021 9:22 AM
2.1.9.3
Issue 1589 - Provided an automated workaround for the known issues with deployment of LWC component bundle files via the Tooling API. Tooling API-based LWC deployment is now enabled by default. If an LWC bundle file is requested for deployment and any non-test JavaScript file in the same bundle imports a custom SObject field or a field from the standard User object, deployment is automatically routed to the Metadata API. Similarly, if Tooling API deployment of an LWC bundle file fails specifically due to a FIELD_INTEGRITY_EXCEPTION with an error message denoting a transitive compilation failure due to an unresolvable reference to a custom SObject or User field, deployment of the entire bundle containing that file is automatically retried using the Metadata API.
In my experience, this seems to provide superior deployment performance for individual LWC bundle files most of the time. I've tested the deployment routing logic extensively and it seems to work very well, but given that it uses a heuristic-based approach, it's possible that there may be variants that are not currently covered. If that's the case, please let me know about these failures–in particular the exact error code and message included in the Tooling API deployment failure response–and I'll update the heuristic accordingly. If you do find this approach to be problematic while waiting for the logic to be updated to cover additional scenarios–or if you're finding deployment performance to be worse than before, perhaps because retries are often needed–you can disable Tooling API deployment for LWC and the Metadata API will be used for all LWC deployments.
Issue 1809 - PMD Apex is now integrated into IC2 as a real-time code inspection as opposed to the bulk inspection integration that has been provided previously. The PMD distribution and ruleset must still be downloaded and registered with IC2's PMD Apex inspection, but once registered, IC2 engages PMD in-memory and reports issues in real-time just as with its own first-class code inspections. Support is also provided for suppression of issues reported by PMD Apex via both @SuppressWarnings annotation and NOPMD end-of-line comment. A demonstration video has been published detailing this new integration.
Issue 1963 - It is no longer necessary to use namespace prefixes in the Anonymous Apex or SOQL Query tool windows when working against a connection to an org with a namespace. Code completion and reference resolution now work in those REPL-style editors exactly as they do in standard editors where the code is inferred to be "inside" the namespace.
Added a new template for SFDX project creation, Illuminated Cloud, that runs the Salesforce CLI force:project:create command with the standard template, then removes all template-generated files that are not relevant for IC2/JetBrains development. For those exclusively using IC2 for Salesforce development, this is now the recommended SFDX project template.
Made several changes in anticipation of the upcoming 2021.3 JetBrains IDE update to help ensure that IC2 is compatible with that release immediately, at least based on the current EAP builds. As new builds are released between now and 2021.3 GA, I will work to ensure continued compatibility.
Other related fixes and improvements.