nushell: Wrong ... expand for some commands
Describe the bug
On go we use ... do indicate all sub-folders: go test -coverprofile=coverage.out -cover ./pkg/...
Cases like this shouldn’t be expanded.
How to reproduce
On any go project you can try to run the tests by doing:
$ go test -coverprofile=coverage.out -cover ./pkg/...
no Go files in /Users/herlon/go/src/github.com/herlon214
Because ... is expanded it tries to run the tests in the wrong folder.
Expected behavior
$ go test -coverprofile=coverage.out -cover ./pkg/...
ok github.com/herlon214/sonarqube-pr-issues/pkg/scm 0.179s coverage: 87.7% of statements
ok github.com/herlon214/sonarqube-pr-issues/pkg/sonarqube 0.234s coverage: 81.1% of statements
Screenshots
Configuration
| key | value |
|---|---|
| version | 0.61.0 |
| branch | main |
| tag | v0.5.1 |
| short_commit | 87c684c7 |
| commit_hash | 87c684c7daf06882ddf10a5668f826646a012d93 |
| commit_date | 2022-04-13 18:42:57 +00:00 |
| build_os | macos-x86_64 |
| rust_version | rustc 1.60.0 (7737e0b5c 2022-04-04) |
| rust_channel | stable-x86_64-apple-darwin |
| cargo_version | cargo 1.60.0 (d1fd9fe2c 2022-03-01) |
| pkg_version | 0.61.0 |
| build_time | 2022-04-13 21:33:32 +02:00 |
| build_rust_channel | release |
| features | default, trash, which, zip |
| installed_plugins |
Additional context
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 21 (19 by maintainers)
Should we just disable path expansion on externals altogether? 🤔 I’m wondering if it would break anything but you can always
path expandmanually.I’m thinking we should have a way to disable path expansions. There are use cases where you just want to pass the raw string. For example, recently, I wanted to remove a directory named
~I accidentally created. It might be quite hard, though, since path expansions happen all over the place.