3) rails-api ( https://github.com/rails/rails/blob/master/actionpack/lib/action_controller/api.rb) is merged into master (though not into 4.2-stable). "ApplicationController < ActionController::API" would would be a very reasonable use case for having no need for capybara. As this is going to part of Rails in the next major release, it seems that Rails applications that only respond_to JSON will become more common. While it's still possible to use capybara for such applications, there are much more lightweight options (such as Webrick + Net::HTTP, which I often use instead of capybara for lightweight sinatra apps). So even if currently most Rails apps use capybara, a growing number of them won't with the next release.
On Tue, Jul 14, 2015 at 12:03 PM, Isaac Betesh <iybet...@gmail.com> wrote: > 1) By the same logic, almost all Rails applications use devise, and bcrypt > is a dependency of devise. > > 2) capybara is not typically a dependency in production > > On Tue, Jul 14, 2015 at 11:29 AM, Rafael Mendonça França < > rafaelmfra...@gmail.com> wrote: > >> Nokogiri is needed for tests and I don't think tests are often used, at >> least they should. I still don't see any reason for doing this even more >> because almost all Rails applications use capybara and nokogiri is also a >> capybara dependency. >> >> On Tue, Jul 14, 2015 at 10:47 AM <iybet...@gmail.com> wrote: >> >>> Thank you for the feedback. Thank you especially to Carlos for pointing >>> out that I could just include ActiveSupport without ActionView. >>> >>> I could have left out the personal anecdote--Ryan makes a good point >>> that the real issue is that nokogiri should not be a dependency when it is >>> needed by only a small subset of functionality, that often is not used at >>> all. >>> >>> So, rails-core team, are you guys on board? >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Ruby on Rails: Core" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to rubyonrails-core+unsubscr...@googlegroups.com. >>> To post to this group, send email to rubyonrails-core@googlegroups.com. >>> Visit this group at http://groups.google.com/group/rubyonrails-core. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Ruby on Rails: Core" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/rubyonrails-core/TqPPisZ3ttU/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> rubyonrails-core+unsubscr...@googlegroups.com. >> To post to this group, send email to rubyonrails-core@googlegroups.com. >> Visit this group at http://groups.google.com/group/rubyonrails-core. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
