CLI: --files parameter is unwieldy
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by locating the CLI argument parsing for the libman install command and how repeated --files values are currently handled. Compare it with the proposed GNU-style behavior, including the case where --destination and foo follow --files; done means multiple file names can be supplied without repeating the option and the existing command still behaves correctly.
Written by the indexing model from the issue text.
Description
Functional impact
It's inconvenient to type --files for every individual file (also, why is --files pluralized if it can only specify one file?)
Minimal repro steps
libman install jquery@3.3.1 --files jquery.js --files jquery.min.js --files jquery.min.map
Expected result
--files ought to be the last parameter, and everything after it should be considered a file name. This proposed behavior is similar to the -- parameter in GNU convention.
The above command could be simplified to:
libman install jquery@3.3.1 --files jquery.js jquery.min.js jquery.min.map
In the following, --destination and foo would be considered file names.
libman install jquery@3.3.1 --files jquery.js jquery.min.js jquery.min.map --destination foo
Actual result
It's tedious.
- Dominant language
- C#
- Stars
- 486
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
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.
More from aspnet/LibraryManager
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aspnet/LibraryManager#824 · 1 comment · 3 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
aspnet/LibraryManager#804 · 2 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
aspnet/LibraryManager#829 · 1 comment · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
aspnet/LibraryManager#820 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
aspnet/LibraryManager#808 · 5 comments ·
All issues in aspnet/LibraryManager
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
apache/arrow-adbc#4809 ·
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/vscode-azurefunctions#5197 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
microsoft/microsoft-ui-reactor#1274 ·