This is a guest post by Junichi Ito (@jnchito). Junichi is a Ruby programmer at SonicGarden.jp, translator of Everyday Rails Testing with RSpec, and one of the most popular Ruby writers/bloggers in Japan
If you use a class as a namespace, it can produce a bug that doesn’t always show up on the surface. You should different names for your model class and your namespace in Rails applications.
class Staff < ApplicationRecord
# Shoud not use class as namespace
class Staff::ItemsController < ApplicationController
# Should use a different name for namespace
class Staffs::ItemsController < ApplicationController
RubyMine 2017.1 (build 171.3780.96) has been released! This is the first major update for RubyMine this year, and we encourage you to learn more about it and get the new version from the What’s new page.
During the Early Access Program, we’ve posted multiple times to describe every change being made in RubyMine, so our frequent EAP users probably already know what v2017.1 has got inside. Here’s just a brief list of all new features with links to the related blog posts: Continue reading
Posted in Announcement
It’s been awhile since we asked your opinion about the future of Ruby and Rails. At last, we are ready to announce the (delayed) results of our community survey.
We were able to get 100+ thoughts from you, and we’d like to share some key findings.
Just to refresh your memory, we asked two fundamental questions:
- What do you think about the future of Ruby and Rails?
- Thinking of an ideal Ruby code editor of the future, what features should it have?
Though these open-ended questions prevented the results from being standardized and no statistically rigorous report could be produced, they helped us understand your thinking better. Also, the second question was perceived by many as “Show some love and name some bugs in RubyMine,” which was both pleasant and very useful for our team. Continue reading
RubyMine 2017.1 RC1 (build 171.3780.26) is now available! This build is the first release candidate for RubyMine 2017.1 which is coming by the end of March.
Besides fixing a number of bugs, this update brings more stable support for Docker, allowing you to work with Rails apps correctly. We’ve already announced support for Docker, and now we’d like to show you exactly how it works in RubyMine.
First of all, be sure to install the Docker plugin right from the IDE (Preferences | Plugins | Browse repositories). This probably won’t take longer than a minute:
RubyMine 2017.1. EAP 9 (build 171.3691.15) is available. Besides fixing a number of bugs discovered in previous 2017.1 EAPs, this update provides a better design for the currently opened tab:
RubyMine 2017.1 EAP 8 (build 171.3566.31) is now available. This early access program brings a couple of important changes: Puppet improvements and Docker support.
You’ve given us some constructive feedback on the previously announced Puppet project structure and improved Puppet support. Keeping it in mind, we’ve tweaked our IDE to make Puppet development with RubyMine smoother.
New Project – Puppet Module
First, we’ve added the ability to create a new Puppet module right from the New Project wizard (File | New Project) so that you can start developing Puppet in a flash:
RubyMine 2017.1 EAP 7 (build 171.3224.24) is out, featuring the new ability to instantly rollback freshly generated Rails entities.
Now when you run rails generators (Tools | Run Rails Generator), e.g. to create a new controller, the IDE provides a quick way to roll the generation back:
This update also fixes a number of bugs, including a regression in the Incorrect call argument count inspection, discovered in the previous EAP.
Download this Early Access Program from our What’s new page. See the release notes for the full list of improvements, and submit any issues to our tracker.
Your RubyMine Team
RubyMine 2017.1 EAP 6 (build 171.3019.14) is out, featuring the long-awaited ability to create tests for Rails entities (controllers, models, helpers, mailers) from the Go to test action. This EAP also brings new parameter hints for Ruby, updated markdown plugin, and support for Cucumber 3.
Creating tests with Go to test
Imagine that for some reason you have a controller without a related test. In this case you can simply use the same Go to test (Navigate | Test) to generate the missing test:
Please welcome another minor update for 2017.1 EAP series:
RubyMine 2017.1. EAP 5 (build 171.2822.20). Download the new version from our What’s New page. If you’re already running RubyMine 2017 EAP 4 (build 171.2613.16), install the patch by clicking Check for Updates.
See the release notes for the list of improvements.
Your RubyMine Team
RubyMine 2017.1 EAP (build 171.2613.16) is available. In this bug-fix update:
- Aggressive Rubocop offenses are now displayed on class/module/method names only, instead of all affected contents.
- We’ve fixed the issue related to choosing the correct testing framework for running spec files.