#JETBRAINS APPCODE REVIEW UPDATE#
#JETBRAINS APPCODE REVIEW MANUAL#

However, I don’t really care about the other 900 or so other unit tests in my application when I’m writing a new one. Of course Xcode has shortcuts for running all of the tests, and usually it doesn’t take too long to run those tests. The only way I’ve found to run a single test in Xcode is to click the tiniest of icons in the breakpoint space of a test file.

#JETBRAINS APPCODE REVIEW UPDATE#

When I update the method, all calls of that method are updated with the new parameter (defaulted to passing NULL or 0). If I need to add a new parameter to a method, I can hit ⌘F6 anywhere that method is used in the code to bring up a modal that allows me to add a new parameter. In AppCode, I can click a file and hit ⇧F6 and voilá, I’m editing the file name and the class name. I have to navigate to the file I want to change, and manually add the parameter.

#JETBRAINS APPCODE REVIEW MANUAL#

Also, refactoring methods to add or remove parameters is completely a manual process in Xcode. If I want to then rename the class, I have to right-click the class name, choose refactor, and then rename it. ⇧⇧ – Find in all project files and display list of recent filesĪnother Xcode oddity that bugs me is that when I rename a file, the class name remains unchanged.You can fuzzy find files using ⌘⇧O, and it works pretty well, but AppCode does it so much better.ĪppCode provides several different file finders: When I’m using a class that already exists but I haven’t imported yet, I can use ⌥⏎ again to add that class to my imports. AppCode even brings up a modal allowing you to change that method’s signature and add or remove parameters. I can then define new methods on that class by hitting ⌥⏎ again. When I’m in the middle of a unit test and I need a new class, I simply declare that class and hit ⌥⏎ and specify where to place it. Finally, I’m ready to navigate to the top of my current file and add the #import 'filename'.ĪppCode takes away all of that pain. Then when I settle on a good method name for that new object, I have to go to the header, declare it, and then stub out the implementation. When I need to create that class in Xcode (to get the tests to compile) I have to find the folder I’d like to add that class to, right click, new file, yadda yadda. Since we practice TDD at Atomic, often times I’m writing tests using classes that don’t exist yet or are not yet imported. When I’m in the middle of writing a test, the last thing I want to do is lose my train of thought.

For the last 6 month, I’ve had the opportunity to use AppCode as my primary IDE, and it is head and shoulders above Xcode.Ĭreating new classes in Xcode is the worst. For a long time, the only IDE that iOS and OSX developers had was Xcode, and life was okay.

Jetbrains appcode review