Warn the user if an alias overrides a custom command or vice-versa
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 40.5k
- Forks
- 2.3k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 85
Description
Related problem
I had a custom command named the same as an alias, and I have been pulling my hair because of it.
In my case it was in the config.nu configuration file.
Describe the solution you'd like
It would be nice if at least a warning, and ideally an error to prevent such issues. Maybe focused on the nu.config file only, since we should let the user override an alias or custom command in the shell without an error (a warning could be nice)
Custom commands with the same name are not allowed, but it would be nice to prevent custom commands and aliases with the same name.
I also noticed you can have multiple aliases with the same name, it would be nice to prevent it too I guess.
Describe alternatives you've considered
No response
Additional context and details
No response
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
The issue names config.nu but no repository files or tests. Start by reproducing collisions between aliases and custom commands, including duplicate aliases, then trace how those definitions are registered or resolved. Done should establish and test the chosen warning or error behavior for configuration files while preserving the stated interactive override behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100