rails-engines

I have a request spec in a Rails engine. The view that is rendered calls a route and passes in a hash, i.e. projects_path(:scope => "user") . A route like this will eventually call url_for , but url_for is defined in many places. When running the application or running a request spec in the main app (root level), the call chain ends up at ActionView::RoutingUrlFor#url_for ; when running a spec in the engine, however, the call chain ends up at ActionView::Helpers::UrlHelper#url_for . In Rails 4, the url_for method defined in UrlHelper no longer accepts hash arguments, so I'm left with this

I'm struggling to understand how Rails 3.2 applies layouts when using mountable engines. Scenario: I'm building an engine which itself has a dashboard view and an admin view for various admin functions. I want the dashboard to have its layout overridable by the base application (if the user desires) but the admin should always use its own layout. Here's what I have at the moment inside my engine; application_controller.rb module Myengine class ApplicationController < ActionController::Base admin/dashboard_controller.rb module Myengine class Admin::DashboardController < ApplicationController

I'm working on a mountable engine for use with Rails 3.1, and I want to list the engine's routes. I created the engine using: $ rails plugin new rails_blog_engine --mountable And edited the 'test/dummy/config/routes' file to read: Rails.application.routes.draw do mount RailsBlogEngine::Engine => "/blog" end ...and 'config/routes' to read: RailsBlogEngine::Engine.routes.draw do resources :posts end I want to list the routes generated for ':posts', but it's not clear how I can do this. When I run 'rake app:routes', I get only the "/blog" route: $ rake app:routes rails_blog_engine /blog {:to=

I have multiple rails applications talking to the same backend and I'd like them to share some migrations. I setup a rails engine (with enginex), I can share anything (controllers, views, models,...) but no migrations. I can't make it work ! I tried to create a file db/migrate/my_migration.rb but in my main application if I do : rake db:migrate It doesn't load them. After some googling it appears there was some recent work on this and it seems this has been merge to rails master. I'm with rails 3.0.3 do you see any way to make this work ? Thanks ! What i do, is add an InstallGenerator that

I started making a Rails 3.1 engine, and I'm having a hard time testing it using rspec. First of all, if I run rails g integration_test whatever it creates a regular integration test in tests/integration instead of spec/requests (the rspec-rails gem is installed and required as a development dependency in the gemspec file) Also, when I run a spec test I get an error saying the table corresponding to the model I'm testing has not been created. I tried rake engine_name:install:migrations and running rake db:migrate from inside the dummy app, and I get a "table already exists" error. Everything

I have found a few articles addressing the issue of helpers within an engine not being accessible to the consuming (parent) application. To make sure we are all on the same page, let's say we have this: module MyEngine module ImportantHelper def some_important_helper ...do something important... end end end If you look at the rails engine documentation in the "Isolated engine's helpers" (L293), it says: # Sometimes you may want to isolate engine, but use helpers that are defined for it. # If you want to share just a few specific helpers you can add them to application's # helpers in