Administering a Comment model about activeadmin HOT 2 CLOSED

That's exactly correct. To get around this, register your Comment class as another name. For example:

ActiveAdmin.register Comment, :as => "User Comments"

Maybe we should consider register ActiveAdmin::Comment as another name.

from activeadmin.

I like the idea of namespacing for anything outside the scope of an app. Of course there will be conflicts everywhere with a name like "comment". In the comfortable_mexican_sofa gem, the models are namespaced in CMS and the tables all have a cms_ prefix. Good idea all around, especially for a gem like this, which will integrate with bigger projects.

On another note, would it make sense to use "app/active_admin/admin" to define resources? If you're defining everything at :root like I am, it doesn't make sense to put it into an "admin" directory. I might end up nesting as well, so it would be great if hierarchy and scope naming was respected within that tree somehow, along with breadcrumbing... eventually, a second-level menu bar would then be possible.

from activeadmin.