For custom commands, allow yakut to read a map file
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 65
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
The file could be yaml or json or ini, but would map commands in words to command numbers. It could be automatically read in from known location like a ~/.yakut/custom_commands.yaml
---
custom_commands:
- number: 300
name: foo
- number: 301
name: bar
This would allow users to do:
yakut cmd X foo instead of yakut cmd X 300 which is not descriptive.
These could be also checked for duplicates and limits (like predefined values).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the command handling for yakut cmd and inspect existing configuration conventions. Define how a known-location YAML, JSON, or INI map is loaded, validated for duplicate names, numbers, and limits, and used by name. Done means yakut cmd X foo resolves the configured number while existing numeric commands continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100