Skip to content
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

Add --error-trace to lucky watch / lucky dev #947

Closed
jwoertink opened this issue Oct 14, 2019 · 2 comments · Fixed by #957
Closed

Add --error-trace to lucky watch / lucky dev #947

jwoertink opened this issue Oct 14, 2019 · 2 comments · Fixed by #957
Labels
clarify api Rename/remove/add something to make the API easier to understand improve error experience Make errors nicer to deal with

Comments

@jwoertink
Copy link
Member

When running your app through lucky dev, there's no way to pass --error-trace currently. We need a way to proxy that down to this command.

We could have lucky dev --error-trace or maybe you just edit your Procfile.dev (which would probably need to happen anyway), and update lucky watch --error-trace.

@jwoertink jwoertink added improve error experience Make errors nicer to deal with clarify api Rename/remove/add something to make the API easier to understand labels Oct 14, 2019
@carcinocron
Copy link

any way to see stack traces before this is merged?

@jwoertink
Copy link
Member Author

@InstanceOfMichael You can just boot your app with crystal src/start_server.cr --error-trace. You just don't get the nice compile watcher, but if you make a change, just kill the server and start back up manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarify api Rename/remove/add something to make the API easier to understand improve error experience Make errors nicer to deal with
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants