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.
Design new CLI usage
See original GitHub issueThe options suggested so far for the CLI executable usage are:
git vfs <verb>vfsgit <verb>vgit <verb>
I currently lean towards vfsgit as the entry point, because it more closely mirrors the name “VFS for Git”.
We need to go through each of our verbs and ensure this design choice makes sense, but I don’t see any obvious issues at the moment.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Command Line Interface Guidelines
An open-source guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.
Read more >Designing a CLI: 11 Principles from the MongoDB Realm ...
1. Allow users to create and clone Realm applications and assets via the CLI. Develop short and easy-to-understand commands for app creation ...
Read more >Designing the Specify CLI
The Specify CLI helps you sync design tokens and assets from Sources, like a Figma file, and to pull them to get a...
Read more >3 steps to create an awesome UX in a CLI application
3 steps to create an awesome UX in a CLI application · Step 1: Design the commands · Step 2: Design the UI...
Read more >Designing CLI Tools - by Emily Goldfein
Designing CLI Tools · Intuitive commands · Consistent naming and command structures (for example, stick to [verb] [noun] commands throughout) ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Then don’t name it as GVFS, name it as Git VFS and tell people to not to shorten it. Both names are different!
Also, I never seen
Git LFSshortened toGLFSin the wild. Have you?I currently lean towards
git vfsas the entry point, because it more closely mirrors thegit lfscommand.I go with the Git VFS for product name too, since Git LFS is a thing!
Then again, it’s too late now! You guys already started naming VFS for Git everywhere!!