Error message: routeHandler.get is not a function
See original GitHub issueI am seeing this error when I open the ember inspector routes tab with an engine mounted into the app, even without navigating to the engine.
I tried to eliminate the error by removing routes/controllers etc from the engine but nothing seems to help. Only when I remove the entire this.mount
statement from the app router the error disappears.
The error is being thrown from this line. The issue is particularly hard to debug as the error is thrown from the chrome extension, which doesn’t let me place breakpoints.
I am using ember and ember-cli 2.12 and ember-engines 0.5.0
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Error message: routeHandler.get is not a function #1173
Open Ember inspector; Click on Routes; See the error routeHandler.get is not a function on the console. Screenshots.
Read more >TypeError: register.route(...).use is not a function
In this case sendVerification seems to be route handler and not a middleware. It's suitable to specify it only for get if /resend/...
Read more >Routing - Express.js
You define routing using methods of the Express app object that correspond to HTTP methods; for example, app.get() to handle GET requests and...
Read more >Using Express.js Routes for Promise-based Error Handling
Find out how to enable promise-based route code and centralize both error ... in every route handler to resolve using a handleResponse() function...
Read more >intercept - Cypress Documentation
The routeHandler function is called whenever a request is matched, with the ... to receive a network error and subsequent requests will //...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hit this as well, thanks for clarifying. @rmachielse nice to make acquaintance btw
FWIW there is already an issue open in the ember-inspector repo about engines support in general. Though there hasn’t been a great deal of discussion. See emberjs/ember-inspector#632