Posts

2.2.8.8 release notes

  2.2.8.8 Issue 2426  - In Apex, it's technically valid to dereference  System.Map.values()  as a single instance of the map's value type, though  only  when the value type is some type of  SObject , e.g.,  accountsByName.values()?.AccountNumber , and  only  when the map has  exactly  one entry. To be blunt, I don't like that allowed idiom for a few reasons. It feels unnecessary and unsafe—pay specific attention to the use of the safe navigation operator before accessing fields of the one-and-only map entry's value—and in order to provide proper support, it muddies the variant code completions offered for the  values()  method to include both instance methods of  System.List  and fields of the map's value type. Having said that, it is allowed and valid, so I've added support for it in IC2's expression type evaluator. Issue 2449  - Added support for email templates created and managed via the Lightning a...

2.2.8.7 release notes

  2.2.8.7 IDEA-2446  - Fixed an issue with the  PMD Salesforce  code inspection when used with  PMD 7.0.0-rc4 . Note that integration with PMD 7.x may continue to be fragile until the final build is released. In the interim, it should always be safe to use the last official build of PMD,  6.55.0 . IDEA-2447  - Resolved an issue experienced by at least one user where GACK / internal server error was causing OST generation to fail while querying external service metadata. WEB-63263  - In the previous release I referenced a bug I'd logged against JetBrains where custom LWC components referenced in ES6 dynamic imports were not resolving properly. Well, it turns out after a bit more digging, that was my problem to solve. This build includes a fix and those references should now resolve properly. Fixed several small issues that could occur when implementing parameterized system types where the type parameters are used as method formal parameters, most n...

2.2.8.6 release notes

  2.2.8.6 Issue 2424  - Winter '24 / API v59.0 updates Updated all SOAP API clients to be based on the API v59.0 WSDLs. Updated the API version used for primary communication with Salesforce APIs to 59.0. Added 59.0 as an available API version number for configured connections. Updated  metadata.xsd  used for validation and code completion in metadata XML files to API v59.0. Updated the OST version number to prompt regeneration for system API changes in API v59.0. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Winter '24 changes. Updated the bundled SLDS CSS and SVG icons to 2.22.0. Updated for new org features, standard value set names, metadata XML file type extensions, etc. Updated all integrated API documentation. Added support for the new  Comparator  interface. Added support for Dynamic LWC components.  NOTE:  I have filed a bug with JetBrains,  WEB-63263 , for an issue I've observed where dynamic imports a...

2.2.8.5 release notes

  2.2.8.5 Issue 2437  - Fixed an issue with variant code completions offered for standalone  new  expressions. Issue 2440  - Added  static final  modifiers to  Canvas.Test  constants. Note that the OST must be regenerated to see the effect of this change. Implemented several improvements and fixes for the Einstein GPT for Developers integration: Added a settings button to the top-right corner of the main Einstein GPT dialog that can be used to configure the following (with more likely to come): Feedback | Include class context information  - When checked, the immediate call to the  feedback  API includes contextual information about the top-level and member declarations of the Apex source file which was active when generation was requested. This is  enabled by default  but can be disabled if you'd prefer not to share this information with Salesforce. Feedback | Include file information  - When set to any value ot...

2.2.8.4 release notes

  2.2.8.4 Issue 2425  - Added support for  Einstein GPT for Developers . To be clear, though, as the underlying feature is currently in an  early beta-level state , so too should this IC2 integration be considered an early beta. The API used to interact with the backing service is absolutely going to change between now and the final release, and  temporary breakages  are pretty much  guaranteed . I will track these API changes closely and update IC2 as needed to keep the integration healthy, but until the API settles, there will likely be short periods during which it goes from working fine to not working at all. If you run into such issues, please let me know and I'll see what changes are required. With that preface out of the way, here are the features: Added the  EinsteinGPTForDevelopers  scratch org feature flag which must be enabled when creating scratch orgs for use with this feature. This feature can be enabled explicitly in non-scratc...

2.2.8.3 release notes

2.2.8.3 Issue 2423  - Fixed an issue that could lead to incorrect/inaccessible constructor/method signatures being added as references. Updated the  Deprecated API usage  code inspection to report usages of declarations marked as deprecated using the  @deprecated  ApexDoc tag as well as the  @Deprecated  Apex annotation. The inspection can be configured for which of these two mechanisms should be reported, with both enabled by default. Updated the  Modifier Agreement  code inspection to detect and invalid combination of the  virtual  modifier and  @Deprecated  annotation. Ensured that the appropriate  SF_*  environment variables are set alongside the corresponding  SFDX_*  environment variables when executing the Salesforce CLI. This build is light on changes because the bulk of my time has been spent  integrating  Einstein GPT  into IC2. At this point I've implemented a pretty much full-...

2.2.8.2 release notes

2.2.8.2 Issue 2418  - Added a number of new configuration options for Apex code generation: Generate ApexDoc  - When checked, automatically includes an appropriate ApexDoc comment for generated  constructors  and  getters/setters . Note that if the  Enable ApexDoc formatting  formatter option is not enabled, the user will be prompted to enable it to ensure that generated comments are formatted correctly. Generate single line methods  - When checked,  getters and setters  are generated as compact single line methods. Note that if the  Keep when reformatting | Simple methods in one line  formatter option is not enabled, the user will be prompted to enable it to ensure that the generated method isn't immediately formatted across multiple lines. Generate Builder Pattern/Fluent API-style setters  - When checked,  setters  are generated according to the Builder Pattern/Fluent API where, after the field value is set, th...