Features

RubyMine 2020.3.4 and 2021.1.1 introduce the concept of trusted projects. It is designed to reduce the risks associated with opening projects from unknown or untrusted sources. Check out this blog post to learn more. As you might already know, when you open a project, RubyMine runs various tools like Bundler, rake, and rails generators that use code from the project. Files from untrusted sources (Gemfiles, for instance) could potentially contain malicious code and therefore pose a security risk. To warn you about situations where potentially malicious code will be automatically run by the IDE,

RubyMine 2019.1 is filled with features and options to help you navigate around your projects quickly without a mouse or touchpad. For example, you can quickly switch between tool windows, go to classes or actions, and open recently edited files. In our Navigate in RubyMine Like a Pro blog post, we show you how to get around using these features. With v2019.1, we’ve added one more capability to your arsenal of convenient navigation. It is now possible to return to recently visited or changed code parts using the new Recent Locations popup. This can be extremely useful if you can only rememb

To get the most recent information about Docker support in RubyMine, refer to our documentation: Tutorial: Docker Compose as a remote interpreter Tutorial: Docker as a remote interpreter RubyMine 2019.1 has a bunch of capabilities which allow you to work with Docker and Docker Compose. You can inspect existing images and containers, quickly edit Docker files using autocompletion, create new images and start services directly from the IDE, and run or debug your application using Docker SDK. Let’s take a look at how to do all this. Enable Docker support Work with images and containers

RubyMine 2019.1 adds support for rbspy – a great sampling profiler for Ruby (many thanks to @jvns!). This post will help you start profiling your Ruby/Rails apps with RubyMine in 5 minutes. Here are the exact steps: Identify the scenario to be analyzed Create a profiler configuration Run the program with the profiler attached Analyze the profiled data Export/Import the profiled data Other options First things first: make sure you have rbspy installed. If it’s not, see this guide to install it for Maс, Linux, and Windows. Now you’re set. Run RubyMine 2019.1 and follow these s

RubyMine 2019.1 EAP (build 191.4738.18) has just been updated. The new build features an ability to view a Call Hierarchy of Ruby methods, and adds support for TruffleRuby. Call Hierarchy TruffleRuby This build features a very handy ability to view a call hierarchy of methods (Navigate | Call Hierarchy), which expands the potential of the Find Usages action. Not only does the Call Hierachy show you all the methods (“callers”) that use the method you are investigating, but it also shows you callers of the callers. Take a look at the following steps to escape this verbal abracadabra

Hi everyone, RubyMine 2019.1 EAP (build 191.4212.20) is now open! We’ve added support for Factory Bot, improved support for polymorphic associations and gems, fixed many issues with version managers, and there’s much more stuff to come from both the Ruby and the IntelliJ platform team. As for the first EAP build, here’s the list of improvements that have been made: Note that support for Factory Bot is now being improved and polished, this will all be covered in detail later on the blog. (more…)

RubyMine has a number of Smart Keys – configurable options that help you avoid extra typing, and navigate through the code faster. Most of the smart keys, like auto-inserting closing brackets and quotes are on by default. However, there are other options you may want to enable. For instance, you may want to stop at parts of `CamelCase` and `snake_case` words when you navigate through the words in your code with ⌥+Arrows / Ctrl+Arrows. To quickly enable this option, invoke Find Action (⌘⇧A / Ctrl+Shift+A) and start typing “use camelhump words”. The IDE will match your query to the related

RubyMine 2018.3 (build 183.4284.145), the final major update this year, is now available! Learn about all the new features on the What’s new page, or watch this video for a brief summary: (more…)

Hi there, RubyMine 2018.3 Beta (build 183.4139.32) is now available for your review. Please check out the new major features in this Beta build, and let us know if you encounter any issues. Here are the most notable changes made for v.2018.3: Code insight I18n improvements Intention actions Refactoring improvements New Darcula Other improvements (more…)

RubyMine comes with a testing suite for running RSpec, Minitest, Cucumber, and other tests based on your current context, and working with them in a friendly graphical user interface. Let’s see how it works in the following example. Run Tests Rerun Failed Tests Test Gutters Navigate to tests and back Run Tests Once your database and test environment are all set up, you can run all tests in your application, directory, or file, or even run any specific test. Simply navigate to the desired scope, and choose Run test(s)… from the context menu. Alternatively, use the keyboard shortcut Ct

RubyMine provides you with a set of intention actions that can help you to quickly fix code smells, convert statements for better code style, add strings to locale dictionaries, use language injections, and do other handy things simply by pressing Alt+Enter. Let's review all the basic and new intention actions added in RubyMine 2018.3. Quick Overview New intentions in RubyMine Quick Overview Let's start with some basic examples: Below is a two-line statement that uses a ternary operator. You can easily convert it to an `if...end` clause, which is considered pref

Hi everyone, RubyMine 2018.2.3 (build 182.4323.73) is now available. This minor release features an ability to explicitly run scripts with `bundle exec`. Previously RubyMine used `RUBYOPT` options to achieve the same result, which caused confusion and issues in specific cases (see RUBY-11434 & RUBY-22247). To explicitly run scripts with `bundle exec`, go to Help | Find Action | Experimental features, and check `ruby.force.explicit.bundle.exec`: Note that this option will be enabled by default starting with v2018.3 (to be released in November 2018). Some other annoying issue