Today we’ve published another bug-fix build for the Rider 2019.1 release. Here are some important fixes we’ve made in the Rider 2019.1.3 build: (more…)

We have already looked at the many new and improved features of Rider! Let's look at even more available in the Rider 2018.3 version. We are going to look at what's new in Code Completion with regards to Package references, configuration files and more! In addition, we will also look at changes with how Rider recognizes and displays TODO patterns. (more…)

ReSharper comes with a To-do Explorer that makes working with TODO comments in code easier. We've seen we can navigate and manage to-do items, export them to a file, and define our own to-do patterns. In this post, let's look at what ReSharper 2017.3 brings to the table. This post is part of a series around working with to-do items in ReSharper. Keep in mind: we can also use Rider to work with to-do items! Working with to-do items in ReSharper Defining to-do patterns in ReSharper Linking to external resources in ReSharper 2017.3 to-do items Linking to external resources in to-do

In our previous post about working with to-do items in ReSharper, we looked at the fact that many code bases have TODO comments in code. We saw how to use ReSharper (and Rider) to find and navigate them. What if we want to define our own type of to-do items in code? Let's answer that question in this post! This post is part of a series around working with to-do items in ReSharper: Working with to-do items in ReSharper Defining to-do patterns in ReSharper Linking to external resources in ReSharper 2017.3 to-do items To-do item patterns To recognize to-do items in code, ReSharper

Have you ever had the need to place a TODO comment in code? Most of us will have. TODO comments are often a temporary reminder to ourselves, a pointer that tells us to continue work on something after finishing something else. A TODO can be a bug, a code smell, an optimization or even a feature. That last category should probably be logged in an issue tracker like YouTrack, JIRA, GitHub issues or Visual Studio Team Services, but the others can usually found in about any code base: // TODO: This needs cleaning up // REMARK: Do not change this code - it comes from my brilliant mind and is

We are happy to announce we've published a new major release of ReSharper Ultimate bundle: please say welcome to ReSharper Ultimate 2017.3. (more…)

Usually, coding and review tasks are logged in an issue tracker like YouTrack, JIRA or Visual Studio Team Services, all systems that can be connected to from within JetBrains Rider. But what with those typical TODO comments? Do they go into the issue tracker? Or should we simply annotate our code with short comments?  Instead of starting a religious discussion, let's look at how we can work with TODO's in our code and IDE to describe these small, code-specific tasks. (more…)

When working on a project, it’s often needed to create a list of tasks for yourself or your team mates. While usually these tasks are described in an issue tracker like YouTrack, some tasks are either too small or too code-specific to describe in an issue tracker. In such case, adding todo comments in source code makes sense. Many developers already use comments in their code to describe these small tasks, typically using a statement like the following: PhpStorm recognizes these comments and will automatically display them in the TODO tool Window (Alt+6 or View | Tool Windows | TODO). F

A few days ago John Lindquist made two screencasts about Local History and TODO features in IntelliJ-based products, which I'd like to share with you, because AppCode is naturally part of IntelliJ family and as such includes this functionality. Local history Local History allows to expand VCS functionality for you, or, if you don't use a version control it'll help you keep track of everything going on with your code! With all the constant changes made to the code, version control systems can only track differences between committed versions, while local changes can slip unnoticed - and tha

Working on a large project it is quite usual to leave some code refactoring or improvement tasks to be done later, have some code left to be reviewed by your colleagues or just mark some places you still have questions about. Especially if you work in a team it is very important to keep yourself and your team informed about all the issues that require attention. Therefore, sometimes you just can’t find all the comments left in thousands of strings and hundreds of files your project contains. TODO comments in the source code help you to keep high performance and have easy access to all the c

Working on a large project it is quite usual to leave some code refactoring or improvement tasks to be done later, have some code left to be reviewed by your colleagues or just mark some places you still have questions about. Especially if you work in a team it is very important to keep yourself and your team informed about all the issues that require attention. Therefore, sometimes you just can’t find all the comments left in thousands of strings and hundreds of files your project contains. TODO comments in the source code help you to keep high performance and have easy access to all the com

There's been a number of new things we've added in IntelliJ IDEA 10.5 related to version control support. You can try them already in a latest EAP build. And here's a quick overview. Do not forget things... TODO! Now you can easily ensure you haven't forgotten to implement a method, and double-check the important places in your code before commit. Just mark those places in code with TODO. IntelliJ IDEA's new "Check TODO" before commit inspection will notify about all new and edited TODO items. It will also confirm about TODO items in the changed fragments (in case they are not actual any mor