luckyframework / luckyframework/lucky

The gen.task task error message isn't pretty

Open
#1,463 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Crystal
Stars
2.7k
Forks
172
PR merge metrics
No merged PRs in 30d

Description

If you run lucky gen.task and forget to provide a name, you'll get the correct error

task_name is required, but no value was passed

but it doesn't look like the other tasks.

Screen Shot 2021-04-08 at 7 59 37 PM Screen Shot 2021-04-08 at 7 59 46 PM

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running lucky gen.task without a name and compare its error output with the other task commands shown in the issue. Trace the gen.task command's error handling, then verify that the missing-name error uses the same formatting as the other tasks.

Written by the indexing model from the issue text.

Assessment

Tech stack
crystal
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.