-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different behaviour using optional param with engine #275
Comments
Version 2.0.3 👍 |
@bogdan Thanks for looking at that so quickly. Most appreciated. Have noticed the routes where we have an engine mounted at "/" are now correct but not others which are mounted inside an optional scope. i.e. the following routes config is now working correctly Rails.application.routes.draw do
constraints(WeddingDomainPatterns) do
mount Planner::Engine, at: "/", as: :wedding
end
end but this section is still not and did not create any diff between v2.0.2 and v2.0.3 after running Rails.application.routes.draw do
constraints(MainDomainPatterns) do
scope "(:store)", store: /au|gb|us/ do
mount Planner::Engine, at: "/", as: :planner
end
end
end Could that be a separate issue? Happy to create a new issue and can provide additional information if you'd like. |
@nickcotton fixed it in 8486232. can you check if it works for you? |
@bogdan Yes, have just tested and seems to be working perfectly for all our use cases now. Thanks, this has been really helpful. |
Hi, noticing a very slight difference in behaviour when upgrading to v2. Have done my best to explain below with a short comparison. For some reason in v2 I'm getting an extra
/
on some paths when I wasn't under the previous version. Entirely possible this is down to user error but thought I would raise anyway.routes.rb
Engine
routes.rb
routes.js - 1.4.9
routes.js - 2.0.2
The text was updated successfully, but these errors were encountered: