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 error message for bad build targets #2384

Closed
sjakobi opened this issue Jul 17, 2016 · 2 comments
Closed

Improve error message for bad build targets #2384

sjakobi opened this issue Jul 17, 2016 · 2 comments

Comments

@sjakobi
Copy link
Member

@sjakobi sjakobi commented Jul 17, 2016

See #2382.

The error message "Could not find a component named warp" could be a lot better:

It could:

  • point out the available targets (or refer to stack ide targets)
  • detect that a target refers to a non-local package
  • link to documentation
@v0d1ch
Copy link
Contributor

@v0d1ch v0d1ch commented Feb 14, 2020

Is this ticket still needed? When running:

stack build --file-watch --test --copy-bins --haddock wai-extra :warp warp:doctest 
  --exec 'echo Yay, it worked!'

I get:

- warp doesn't seem to be a local target. Run 'stack ide targets' for a list of available targets
- Unknown local package: warp

So it seems we have the information that warp is probably not a local target.

If we still need to implement this what should be the best error message here @mgsloan ?

@sjakobi
Copy link
Member Author

@sjakobi sjakobi commented Feb 14, 2020

@v0d1ch Thanks for the update!

I think that error message is good enough to close the issue. Feel free to re-open if you disagree of course!

@sjakobi sjakobi closed this Feb 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants