New AppCode 2017.2 EAP: Extract Method refactoring for Swift and support for Xcode 9 documentation format

Posted on by Stanislav Dombrovsky

Hi everyone,

New AppCode 2017.2 EAP (build 172.3317.17) is available for download on our site (if using previous 2017.2 EAP build, the patch update is also available).

Extract Method for Swift

This build brings one of the most important features from our roadmap, an initial implementation of Extract Method refactoring for Swift! Select the code you want to extract, press ⌥⌘M, and type the method name:
Extract Method start
Click on the row with parameter name to change it or add an internal name:
Edit parameters
Change the method/function visibility as you want:
Set visibility
Press enter and have your code replaced with the method or function call you have just created:
Finish Extract Method

Note, that some issues still exist and we are working on them.

Besides, this build also brings support for Xcode 9 documentation format, fixes the issue when test output was empty when running UI tests with Xcode 9 set in AppCode preferences, and addresses some regressions found during our testing.

For the full list of fixes please see the release notes.

Your AppCode team
JetBrains
The Drive to Develop

Comments below can no longer be edited.

10 Responses to New AppCode 2017.2 EAP: Extract Method refactoring for Swift and support for Xcode 9 documentation format

  1. AMS says:

    July 6, 2017

    Thank you for this release !
    I have a question about he color scheme you are using in the GIFs: is it available somewhere ?

    • Stanislav Dombrovsky says:

      July 7, 2017

      It’s a default Darcula scheme + Preferences | Editor | Color Scheme | Language Defaults | Semantic highlighting turned on

  2. Bill A says:

    July 6, 2017

    EXTRACT METHOD! YES!

    Thanks, guys!

  3. Alex says:

    July 7, 2017

    Hi team, thanks for the frequent updates!

    Are there any plans to resolve the obj-c/swift interoperability false warnings and errors?
    http://www.goloskok.com/u/image-Q7lgUpkjXv.png

    Parameter type mismatch, Incompatible pointer types, Cannot resolve method, False Unused import statements, Types are not compatible, Taking pointer from integer without a cast, Integer expression required in switch..

    I’m sure many product focused companies would be reusing a lot of their obj-c codebase, and it’s been months and months waiting for these to get resolved..

    • Stanislav Dombrovsky says:

      July 7, 2017

      Most of them are related to resolution issues, we are working on them, but it’s impossible to resolve all of them at once. It’s a part of Objective-c to Swift translation. About the screenshot – it’s much better for us to have an access to your project or sample with the most annoying issues, so we could investigate them and fix. If it’s possible for you, it will be great for us to have it.

  4. hai says:

    July 7, 2017

    awesome 😀

  5. Faisal says:

    July 10, 2017

    I keep checking every update to see if firebase import issue is fixed and I keep getting disappointed.

    • Stanislav Dombrovsky says:

      July 10, 2017

      We are working on related base issues, regarding this one – we need more time to fix it.

Subscribe

Subscribe to product updates