> On Mar 10, 2018, at 9:39 PM, Robert Phillips <robert.phillip...@gmail.com>
> On Friday, 9 March 2018 14:58:23 UTC, fugee ohu wrote:
> >Why create an ApplicationRecord class inheriting from ActiveRecord::Base and
> >then have all models inherit from ApplicationRecord instead of
> >ActiveRecord::Base ?
> I know a guy that doesn't use rails generate controller or rails generate
> model.. So when he makes a controller he just handcodes it.
> For him I suppose it'd be an advantage, as
> It is easier to write
> class Abc < ApplicationController
> than to write
> class Abc < ActionController::Base
> protect_from_forgery with: :exception
It's meant to be a way to gather common features into one place. If all your
routes are meant to have CanCanCan protecting them from unauthorized access,
then you may see this in the ApplicationController:
Which means that you won't forget to add that to your controllers and leave
something important exposed to the public. There's lots of other useful stuff
you can wedge in the ApplicationController that you need in all controllers,
and thus only have to write once. Inheritance can be useful!
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-talk+unsubscr...@googlegroups.com.
> To post to this group, send email to firstname.lastname@example.org.
> To view this discussion on the web visit
> 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: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.