Saroj Maharjan
Saroj Maharjan
```ruby RUBY_VERSION => "2.5.1" Rails.version => "5.2.0" ``` ```ruby # User.rb has_one :profile, dependent: :destroy accepts_nested_attributes_for :profile # Event.rb belongs_to :user has_one :profile, through: :user accepts_nested_attributes_for :user ``` Given above...
Prefer `exists?`instead of `present?` for checking record according to [this blog post](https://semaphoreci.com/blog/2017/03/14/faster-rails-how-to-check-if-a-record-exists.html). > ... `exists?`, is even more optimized, and it should be your first choice when checking the existence...
It would be great to have a simple cli help doc. ``` gel -h gel --help ```
Feature Request: How about adding an option to unpessimize i.e. remove version specification from Gemfile? This is useful in case when you want to update old Gemfile and running bundle...
1. https://speakerdeck.com/timmoore/embracing-capybara?slide=18 2. https://robots.thoughtbot.com/write-reliable-asynchronous-integration-tests-with-capybara 3. https://gist.github.com/zhengjia/428105 4. https://robots.thoughtbot.com/automatically-wait-for-ajax-with-capybara
```[ruby] bin/rails assets:precompile ✭ ◼ ruby(27988,0x10c21d5c0) malloc: *** malloc_zone_unregister() failed for 0x7fffb09db000 ```
* _Before_  ___ * _After_ 
This will allow new additions to be tweeted automatically or open other possibilities like sending out emails notifications to subscribers, IFTTT etc.