It was a great pleasure for the RubyMine team to participate in RailsConf 2017 and meet so many of you there!
One of the most important things long-time participants discovered was the dominating number of first-time attendees, which signifies unfailing interest in Ruby on Rails.
About a hundred attendees participated in a small survey we conducted to figure out the most popular editors and technologies used besides Ruby and Rails. Here are the results:
As always, this year the RubyMine team will again participate at RailsConf! Meet us at booth #315 near the middle of the Expo hall, next to the coffee spot. We will be wearing our JetBrains T-shirts so you can easily find us around the show.
We’ll be glad to answer your questions, hear your issues and suggestions, and chat about the future of Ruby on Rails and RubyMine. You will also get a chance to take a quick survey and win a free personal RubyMine license. And surely we’ve prepared some swag for you, so you won’t leave empty-handed 😉
Follow us on Twitter and join our newly created RubyMine Slack to stay tuned for updates!
Hope to meet you at RailsConf 2017!
Your RubyMine Team
RubyMine 2017.1.2 RC (build 171.4249.23) is out, featuring the ability to differentiate hash curly braces from block curly braces using special check-boxes in settings (Setting/Preferences | Code style | Ruby | Other):
We have just set up RubyMine Slack, and we encourage you to sign up for it! Get your invitation, and please take a look at the simple guidelines below.
RubyMine Slack Guidelines
This chat was created as a place for communication between RubyMine users. Use it to ask for help, suggest improvements for the product, share your projects / use-cases / best practices, and discuss Ruby and Rails trends. The RubyMine team may also use it for product announcements and updates. Continue reading
We have updated the stable version to RubyMine 2017.1.1. and we recommend updating to it as it fixes the painful RSpec regression, performance issues, and other bugs. Read more there.
We are working on the next version and in this post we’d like to announce RubyMine 2017.1.2 EAP (build 171.4249.6) which brings the following improvements:
This EAP build should fix the issues with the resolution of Puppet modules which surfaced after updating to v2017.1 and made users downgrade:
RubyMine 2017.1.1 RC (build 171.4073.36) is released. This update fixes the performance issues that many users reported after updating to v2017.1.
- Fixed a regression that broke running different scenarios within one RSpec file.
- Fixed code style issues, namely the Spaces around curly braces setting that adds or removes spaces around curly braces in code blocks, and the ability to keep line breaks which didn’t work with when… then.
- Fixed minor issues with RuboCop.
Download this version from our EAP page on Confluence.
See the release notes for the full list of changes and use our tracker to submit any issues you encounter.
Your RubyMine Team
Posted in Announcement
RubyMine 2017.1.1 EAP (build 171.4073.18) is available to fix a painful regression that prevented running RSpec tests from context in the recently launched RubyMine 2017.1. Now it works just fine.
As for other fixes, the inability to “Select all” that might have affected some users has been fixed. The fonts that lost anti-aliasing in v2017.1 have also become smooth again across all JetBrains IDEs. Continue reading
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