Closed horx closed 9 years ago
hey there. sorry that you ran into this, but good news! I already have a fix and just need to push the proper commits, which I should be able to do today.
I should add that if you're looking for a more technical explanation of what's causing the issue, take a look at #69. The fix I have includes the change to HttpRouter
and the router generator (the expression plug Plug.Debugger
should be use Plug.Debugger
).
Moving from plug Plug.Debugger
to use Plug.Debugger
will definitely require #69 to be addressed. Can confirm that ripping out HttpRouter
's defoverridable ...
does fix the issues that crop up with that (thus revealing sexy purple Railsy error pages instead of ugly compilation errors :) ).
Hey @Horx, I just pushed the remaining fixes to correct this issue. Make sure your deps are up to date with their respective Hex versions (sugar
should be at 0.4.7 and http_router
should be at 0.0.5) and that the plug Plug.Debugger
is updated to use Plug.Debugger
in your router.
Let me know if you're still running into issues.
@slogsdon Yes, U have do it as you said, The error doesn't appear any more.
But question, The Debugger
does not show any log in console after I restarted my app, I‘m not familiar with Debugger
, should I add some options to the Debugger
or something else ?
@Horx Debugger is less of a console thing and more of an error page thing. Plug.Debugger
is basically Elixir/Plug's equivalent to the fancy error pages that Ruby on Rails (for example) will show you in a development environment, like so:
In the above-screenshotted example, my cleverly-named :asdf
application throws an error whenever someone tries to access localhost:4000/ohno
(which does nothing other than raise "oops"
); with Plug.Debugger
, the above page is displayed, providing me with immediate debugging information right from the browser. Pretty nifty.
@slogsdon @YellowApple I got it . Thanks for your patience.
@Horx Great to hear! let us know if you run into any other issues.
Hi, when I set the
show_debugger
option totrue
in config.ex, then restart the server, It always raise exception like this:and the version of
Sugar
in my app is0.4.6
. Did I do something wrong ?