I'm looking at the behavior demonstrated in:
test_rails_app/app/controllers/admin/
blog_posts_custom_new_and_edit_controller.rb
You'll see that in this controller, there are Controller#new and
Controller#edit methods defined, which admin_assistant sees and
decides to generate a New link and Edit links. This occurs even though
thew :new and :edit actions aren't included in the config.actions
declaration. It treats defining the method as sort of an implicit
configuration.
I have a use case that doesn't work well with this implicit
configuration, so I wanted to see what you all thought about requiring
actions to be in the actions array in order to generate links to them.
Here's my use case:
In my admin area, I want a list of Recommendations (auto-generated by
admin_assistant).
In-context in the content area of my app, I want a user with admin
privileges to be able to create a new recommendation by clicking a
link to a new form with query params that specify the content to be
recommended.
That in-context click is a GET to the :new action of the admin
recommendations_controller, which is triggering the undesired (in my
case) behavior I described above.
Anyone opposed to changing this? Other ideas?
Cheers,
Luke
--
Luke Melia
lu...@lukemelia.com
http://www.lukemelia.com/