Ayush Singh ad125abf6a fixes which showing aliases as built-in nushell commands (#9580) ... fixes #8577 # Description Currently, using `which` on an alias describes it as a nushell built-in command: ```bash > alias foo = print "foo!" > which ls foo --all ╭───┬─────┬──────────────────────────┬──────────╮ │ # │ arg │ path │ built-in │ ├───┼─────┼──────────────────────────┼──────────┤ │ 0 │ ls │ Nushell built-in command │ true │ │ 1 │ ls │ /bin/ls │ false │ │ 2 │ foo │ Nushell built-in command │ true │ ╰───┴─────┴──────────────────────────┴──────────╯ ``` This PR fixes the behaviour above to the following: ```bash > alias foo = print "foo!" > which ls foo --all ╭───┬─────┬──────────────────────────┬──────────╮ │ # │ arg │ path │ built-in │ ├───┼─────┼──────────────────────────┼──────────┤ │ 0 │ ls │ Nushell built-in command │ true │ │ 1 │ ls │ /bin/ls │ false │ │ 2 │ foo │ Nushell alias │ false │ ╰───┴─────┴──────────────────────────┴──────────╯ ``` # User-Facing Changes Passing in an alias to `which` will no longer return `Nushell built-in command`, `true` for `path` and `built-in` respectively. # Tests + Formatting # After Submitting		2023-07-08 10:48:42 +02:00
..
src	fixes which showing aliases as built-in nushell commands (#9580)	2023-07-08 10:48:42 +02:00
tests	fixes which showing aliases as built-in nushell commands (#9580)	2023-07-08 10:48:42 +02:00
Cargo.toml	REFACTOR: move the 0% commands to nu-cmd-extra (#9404)	2023-07-06 08:31:31 -07:00
LICENSE	Fix rest of license year ranges (#8727)	2023-04-04 09:03:29 +12:00