AppCode 3.4 EAP opens: OptionSetType support, “Set value” for Core Data and more!
Today we are excited to announce the launch of AppCode 3.4 EAP and the first build is already available on our confluence page. Please note that a patch from the release version will not be available until AppCode 3.4 gets stable. This EAP does not require an active license, so you can use it for free until the build expiration date.
This build delivers the following features and improvements:
- Parsing, completion and resolve for types conforming to OptionSetType protocol (OC-12078):
- Parsing, completion and resolve for Self type (OC-12913):
- Set value in Swift debugger for Core Data objects (OC-12896):
- Resolve for enum members in if-case statement (OC-12878)
- Resolving enum initialisers (OC-12639) and parsing named arguments in tuple patterns (OC-12985)
- Fix for Swift Structure View freeze (OC-11526)
Now the Quick Documentation popup (available via F1) also shows documentation for lambda expressions (but mind the remaining problem CPP-5491), namespace aliases (CPP-682) and explicit instantiation. This EAP build also addresses some problems with quick documentation in C++, like the internal error that would previously occur while fetching documentation for anonymous class/struct/enum.
Source directories management
New context menu called Mark directory as is available for folders in Files view:
- Mark directory as excluded. You can choose this option for 2 different cases. First is when you want to remove some directory contents from Inspect Code, Find in Path (⇧⌘F) or Search Everywhere (Double ⇧) results. By default these actions are executed not only on files included into Xcode project, but on all files that are located in the project root folder (except build directories like DerivedData). Second is when you have a source folder included into your Xcode project and you don’t want AppCode to index it. AppCode indexes all directories listed in your Xcode project in order to provide you with accurate code completion, navigation, refactorings and other smart features, but sometimes the source folder can be too big and indexing can become too expensive – in this case you can tell AppCode to manually exclude such folders from indexing.
- Mark directory as library. If you have framework sources included into your Xcode project (or workspace), you may want to disable refactorings for it and take control over navigation and search options. If you mark some folder as a library, refactorings for sources in this folder will be disabled, as will code generation options and completion. By default, results from this folder will not be shown for Navigate to File, Class or Symbol actions. However, if you still want to navigate to the library sources, you can simply tick “Include non-project items/symbols/files” and the corresponding items will be shown in the navigation dialog.
- Mark directory as project sources. In some situations this action can also be helpful – for example, if you want to get navigation and completion for some sources located in your project’s folder but not included into the currently opened Xcode project.
A couple of new features are included into this build:
- By-word difference highlighting in Diff viewer:
- Checkout with Rebase Git action, helpful in case you want to rebase a feature branch on master in one click:
In one if the recent blog posts about AppCode 3.3.3 RC we’ve mentioned that there were some critical issues with debugger when using it with Xcode 7.3 beta 2. These issues should be fixed in this EAP build, so you can use it with the latest Xcode beta.
Note, that starting from AppCode 3.4 EAP minimal Xcode version supported by AppCode will be limited to Xcode 7.2. To use AppCode with earlier Xcode versions (for example, Xcode 7.1.1), please install AppCode 3.3.3.
Java Runtime Environment used with AppCode
IntelliJ Platform has migrated to Java 8 as the target platform. In practical terms this means the following:
- AppCode won’t start under JDK versions older than 8. In general it shouldn’t be a problem for you, since AppCode installer contains an appropriate bundled JDK version.
- In case you’ve switched the Java version used for running AppCode to a non-bundled one (via Switch IDE boot JDK…) and then imported these settings while starting the AppCode 3.4 EAP, you may receive the ‘unsupported Java version’ error. To fix the problem simply delete ~/Library/Preferences/AppCode34/appcode.jdk. In future versions we’ll try to handle this situation automatically (IDEA-149618).
- Plugin writers will be able to use Java 8 features in their plugins.
- The annoying issue with Java2D Queue Flusher thread crashing is fixed in this JDK version.
- Support for RTL languages (Arabic and Hebrew) added to the editor.
- CoffeeScript and Stylus plugins bundled in AppCode.
- Improved UI for Attach to local process… action:
Your AppCode team
The Drive to Develop
AppCode 2023.1 Bug-Fix Update
Hi, AppCode 2023.1 has just been released with fixes for Xcode 14.3 compatibility, Swift refactorings and intentions, the IDE’s UI, and Kotlin Multiplatform Mobile. On December 14, 2022, along with the AppCode 2022.3 release, we sunsetted the product and stopped sales. While we’ve refocused the te…
AppCode 2023.1 Release Candidate
Hi, On December 14, 2022, along with the AppCode 2022.3 release, we sunsetted the product and stopped sales. While we’ve re-focused the team's efforts in other directions, we’ve kept providing technical support to our current users and are releasing bug-fix updates in 2023, targeting mostly the Xco…
AppCode 2022.3 Release and End of Sales and Support
AppCode 2022.3 has just been released. With the release of v2022.3, we are sunsetting the product.
AppCode 2022.3 Release Candidate Is Here
Hi everyone, The release of AppCode 2022.3 is approaching, and the release candidate (build 223.7571.233) is now available for download on our website. You need to have an active subscription or activate a free trial to use this build. The main highlights of this build include: We fixed the r…