question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Usability issues (behave like normal CLI applications please)

See original GitHub issue

I’m submitting a feature request

The usability of the cli is really bad. Some extremly annoying behavior that is not common for cli-applications (at least not outside the Javascript world):

  • Running au does a clear of the screen. Extremely annoying! You should not decide for the user to clear the screen.
  • The help output is different depending on context. Very bad. For example, I have run into buggy scenarios where aurelia-cli does not recognize it is in an existing aurelia-project and gives “new” and “help” as the only options. All command line options should be shown when running help, it should not be context dependent. At least have a “full_help” command or something if it’s so important to hide things for the user.
  • If I have au installed globally, and run it in a project directory, it fails to recognize it as a project??? I first have to run yarn and install it as a local dependency to get things to work. If there is some reason for this, at least a helpful error should be shown about this.
  • The version is not displayed when running the cli. Which is normal for all command line tools pretty much.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:1
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
JeroenVinkecommented, Mar 19, 2018

I agree with everything except the context-aware help command. au new is only relevant when you’re not inside a project directory. It’s not useful to show au build outside of a project directory, or to show au jest as an option when your project is not setup for jest.

0reactions
avrahamcoolcommented, Mar 20, 2018

maybe au help --full? the list will be pretty big, but maybe it can be braked down to section regarding the context in witch you can potentially run au? it’s a bit clunky…

Read more comments on GitHub >

github_iconTop Results From Across the Web

Best Practices Building a CLI Tool for Your Service - Zapier
Zapier support engineer Jacob Blakely advises that usability and discovery are paramount in a CLI application. That experience begins in the ...
Read more >
Designing Better Error Messages UX - Smashing Magazine
As it turns out, a strategic and thorough design of these messages ... There are a few common usability issues with toast error...
Read more >
Visibility of System Status (Usability Heuristic #1)
When we understand the system's state, we feel in control — we can rely on the system to act as expected in all...
Read more >
Should I include a command line mode in my applications?
You should include a command line interface in your application, if it enhances usability and comfort. For instance, calling a CLI command might...
Read more >
Understanding Usability – OSnews
Another non-UI Usability Problem is the issue of deployment. ... For example, a typical server application like Apache needs to be integrated fairly...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found