2.2.7.8 release notes
2.2.7.8
- Issue 2354 - Fixed an issue with automatic import of custom LWC components in ES6+ files. Now the user will be prompted for the correct module import statement as well as the previous incorrect statement that referenced a relative file path (unfortunately I could only add the former so the latter is still offered).
- Fixed the file type association for
*.networkBranding
which was previously associated with both the XML and JSON file types. Now it is only (properly) associated with the JSON file type. Note that it may not automatically associate in an upgrade scenario due to restrictions around automated file type association changes. If so, just add*.networkBranding
to the JSON file type explicitly in Settings / Preferences > Editor > File Types. - Removed the IC2-specific custom module type as that is now a retired concept in the JetBrains plugin SDK. In general this change should be invisible to all users other than that newly-created projects and modules will use the
GENERAL_MODULE
module type or the IDE-specific module type, e.g.,WEB_MODULE
,PYTHON_MODULE
, etc., in their.iml
files instead of theIlluminatedCloud
module type. - Addressed other internal updates suggested by the IDE/plugin SDK based on more stringent guidelines in 2023.2+.