You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PR here #588 seems to have unintended consequences with controller query params.
Since upgrading to v8.0.1 we're seeing this error:
ERROR: Uncaught Error: Assertion Failed: You attempted to generate a link for the "tasks" route, but did not pass the models required for generating its dynamic segments. Assertion Failed: You're not allowed to have more than one controller property map to the same query param key, but both tasks:dueStatus and tasks.index:dueStatus map to due-status. You can fix this by mapping one of the controller properties to a different query param key via the as config option, e.g. dueStatus: { as: 'other-dueStatus' }
Hmmm sorry about that @fran-worley, but thank you for reporting!
I'm trying to figure out why that would have caused the issue you are seeing. Anything special about your setup? Is there a file at app/tasks/index.js? Are you using pods (with or without a podModulePrefix)? Where on disk is that controller that you expect to get resolved?
The PR here #588 seems to have unintended consequences with controller query params.
Since upgrading to v8.0.1 we're seeing this error:
For reference our controller def looks like this:
The text was updated successfully, but these errors were encountered: