1.7.8.0 release notes

[Scott]

Wow...I really have not used the announcements feed at all!  The last (and only!) announcement was when I first released this over a year-and-a-half ago.

I do want to post the release notes for 1.7.8.0, though, as it's perhaps the largest single update I've made, in particular because it's not just additive, but it also makes significant changes to the existing product features.  It's probably a good idea to review the nature of this release to understand how things work and where things can be found after the update, so I'm including the release notes below.

Regards,

Scott

=================================================

1.7.8.0

• Issue 97 - Connections are now configured at the application level instead of the project level:
• When an existing project is opened for the first time, its connections are automatically upgraded to be global. Connections with the exact same name and configuration are merged. If global connections exist for the same username, the user is prompted to select an existing connection or create a new global connection. Otherwise a new global connection is created from the project connection.
• Now only connection names are stored in the project- and module-level configuration files (.idea/illuminatedCloud.xml and moduleName.iml respectively). Connection credentials and other details are now stored in the application-level illuminatedCloud.xml.
• Application-level settings including connections can be exported and imported using IntelliJ IDEA's standard File>Export/Import Settings... feature by choosing the IlluminatedCloud component.
• When a connection referenced by a project or module cannot be resolved, Illuminated Cloud will prompt the user to choose an existing connection or create a new connection.
• All configuration UIs have been updated accordingly for this change:
• Connection management is now available under application settings.
• Project connection configuration is now simplified.
• Module facet configuration now includes only subscription management with a read-only view of the selected connection and development package.
• IMPORTANT - If any problems occur during the upgrade of a project that cannot be resolved using the standard Resolve link, please send your idea.log (Help>Show Log in Explorer/Finder/Files) to me. The upgrade process automatically logs at a sufficient level to facilitate a quick resolution.
• Issue 221 - User-specific and user-independent configuration information are now physically segregated to facilitate team development and configuration sharing through version control:
• After each project is upgraded, its .idea/illuminatedCloud.xml and moduleName.iml files should be safe to check into version control with no information removal required.
• As described above for issue 97, all project-level connection configuration has been moved to the application level and can now be found in userHome/.IntelliJIdeaXX/config/options/illuminatedCloud.xml (Ultimate Edition) or userHome/.IdeaICXX/config/options/illuminatedCloud.xml (Community Edition).
• All other user-specific configuration has been moved into the project's .idea/workspace.xml. This file is not intended to be checked into version control or shared with other users.
• For more information about how to manage IntelliJ IDEA projects under version control, see https://intellij-support.jetbrains.com/hc/en-us/articles/206544839-How-to-manage-projects-under-Version-Control-Systems.
• Issue 446 - Added the ability to perform retrieve operations without the need for a directory diff if desired:
• In IntelliJ IDEA 13+, the new project/module wizard now includes a Merge retrieved metadata checkbox. This option is disabled by default to optimize for the typical experience of seeding a new project/module with metadata from an existing org.
• The Retrieve Metadata dialog now includes two buttons, Retrieve and Merge and Retrieve. The former gives the exact same behavior as before with a directory diff displayed after retrieval; the latter retrieves directly into the project source root, overwriting existing files and creating new files as appropriate. The last selected action is retained across retrieve operations.
• The Retrieve Metadata dialog also includes options for how the package.xml file should be handled when retrieving metadata directly into the project source root. This is because the package.xml file included in a retrieval response may not match the local package.xml file, especially when the local file has been carefully hand-crafted and/or includes wildcards. The last selected option is retained across retrieve operations. The options for how the package.xml file should be handled are:
• Replace - replaces the local file with the retrieved file.
• Merge - opens the configured file diff tool to merge the retrieved file into the local file.
• Skip - makes no changes to the local file.
• Major enhancements to Visualforce/Lightning JavaScript and CSS development when using IntelliJ IDEA Ultimate Edition:
• JetBrains' powerful JavaScript and CSS editors are now fully aware of the standard Salesforce JavaScript and CSS frameworks resulting in significant improvements to code completion, reference navigation, quick documentation, etc.
• It's worth noting that JetBrains' JavaScript editor benefits greatly from JSDoc headers--in particular type hints for parameters and return types--for purposes of type inference. Developers are strongly encouraged to annotate types, variables, and functions with JSDoc for the best editor experience.
• Issue 298 - Significantly improved handling of failed logins due to invalid credentials.
• Issue 271 - Hide meta.xml files by default in the project view. Can be toggled using new Show meta.xml Files menu action.
• Issue 284 - New dialogs used for display of potentially long lists of files and/or metadata.
• Issue 532 - Added support for StandardValueSet metadata type.
• Overall UX improvements.
• Numerous fixes for minor issues.