Global shide directory, ~/.config/shide
Open
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Allows specifying commands that can be used in any project; has its own node_modules, and shide version.
Name conflicts between local and global? Maybe command 'foo' would be `shide-user:foo` or `shide-global:foo` instead of `shide-command:foo`.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name any files, tests, or entry points. First clarify the design for a global ~/.config/shide directory, its node_modules and shide version, and how local/global command name conflicts should work. Done should include an agreed scope and behavior for these cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100