/stack

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

Open
sjakobi opened this Issue Jul 17, 2016 · 0 comments

Comments

Assignees
No one assigned
Labels
awaiting pull request component: options parsing component: output (UI/UX) newcomer friendly
Projects
None yet
Milestone
  P2: Should
2 participants
@sjakobi @mgsloan
@sjakobi
Contributor

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

@sjakobi sjakobi added newcomer friendly awaiting pull request component: output (UI/UX) labels Jul 17, 2016

@sjakobi sjakobi added this to the P2: Should milestone Jul 17, 2016

@sjakobi sjakobi referenced this issue Jul 17, 2016

Open

Can't use component syntax with hackage package TARGETs #2382

@mgsloan mgsloan added the component: options parsing label Jul 19, 2016

@mgsloan mgsloan referenced this issue Sep 28, 2016

Closed

Systematic cleanup and colorization of stack output #2650

0 of 8 tasks complete

@bar9 bar9 referenced this issue Dec 22, 2016

Merged

friendlier error message (Improve error message for bad build targets #2384) #2850

mgsloan added a commit that referenced this issue Jan 6, 2017

@mgsloan
Merge pull request #2850 from bar9/master 
friendlier error message (Improve error message for bad build targets #2384)
Loading status checks…
ca3b70d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment