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

Improve server error messages #46

Closed
LPGhatguy opened this issue Mar 25, 2018 · 0 comments
Closed

Improve server error messages #46

LPGhatguy opened this issue Mar 25, 2018 · 0 comments
Assignees
Labels
scope: cli Relevant to the Rojo CLI
Milestone

Comments

@LPGhatguy
Copy link
Contributor

Some of the error messages Rojo has are pretty bad; any place where Rojo can panic, those error messages should be customized in each case to make things more obvious.

For example, if a partition target is missing on the filesystem, you get:

$ rojo serve
Using project from ...
Server listening on port 8000
thread '<unnamed>' panicked at 'Unable to watch path!: Generic("Input watch path is neither a file nor a directory.")', src\libcore\result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.
@LPGhatguy LPGhatguy added the scope: cli Relevant to the Rojo CLI label Mar 25, 2018
@LPGhatguy LPGhatguy self-assigned this Mar 25, 2018
@LPGhatguy LPGhatguy added this to the v0.4.0 milestone Mar 27, 2018
Dekkonot pushed a commit to UpliftGames/rojo that referenced this issue Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: cli Relevant to the Rojo CLI
Projects
None yet
Development

No branches or pull requests

1 participant