AppCode 3.2 EAP, build 141.2454: quick documentation in Swift


New AppCode 3.2 EAP, build 141.2454 is available for download. The patch update is also available if you are using previous 3.2 EAP build.

The most notable feature in this build is Quick Documentation in Swift. To see the relevant documentation, just press F1 – the documentation displays in a pop-up window with clickable links to other resources. The content includes:

  • standard documentation from Apple DocSets:
  • your own documentation comments (use standard ‘///documentation’ format),
  • classes, protocols and functions signatures, enums, type aliases, etc.:
  • and even inferred type for constants and variables:

One of the previous AppCode EAP build introduced code resolve for custom Swift frameworks (like Alamofire), but thanks to our EAP users we’ve found out that it was not working correctly in case such framework was installed through the CocoaPods. This build includes a fix for this problem.

The full list of improvements can be found in our tracker.

Develop with pleasure,
The AppCode Team

This entry was posted in Announcement, Early Access Preview and tagged , , . Bookmark the permalink.

9 Responses to AppCode 3.2 EAP, build 141.2454: quick documentation in Swift

  1. Bill says:

    This is a great addition – makes a huge difference!

  2. Bill A says:

    Does this support keywords? For example:

    /// Crop function
    /// parameter rect:the rect to crop
    /// returns:cropped rect
    func crop(rect: CGRect) -> CGRect {
    // ….

    should show a formatted tooltip like in Xcode

  3. John says:

    My non-CocoaPods frameworks that were not resolvable in the previous build are now resolvable too. Thanks!

  4. Jens Kohl says:

    Yepp, resolving CocoaPods-installed frameworks works now for me. This is a huge efficiency boost for me, thanks.

  5. Matt says:

    So far this EAP is performing very, very well. No 100% background CPU usage, no one minute wait when getting an exception when debugging, and autocomplete seems much peppier. Great work!

Leave a Reply to John Cancel reply

Your email address will not be published. Required fields are marked *