You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
35 lines
1.3 KiB
35 lines
1.3 KiB
---
|
|
name: v2 feature request
|
|
about: Suggest an improvement for v2
|
|
title: 'your feature title goes here'
|
|
labels: 'type/feature, area/v2, status/triage'
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
## Checklist
|
|
|
|
* [ ] Are you running the latest v2 release? The list of releases is [here](https://github.com/urfave/cli/releases).
|
|
* [ ] Did you check the manual for your release? The v2 manual is [here](https://github.com/urfave/cli/blob/master/docs/v2/manual.md).
|
|
* [ ] Did you perform a search about this feature? Here's the [Github guide](https://help.github.com/en/github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests) about searching.
|
|
|
|
## What problem does this solve?
|
|
|
|
A clear and concise description of what problem this feature would solve. For example:
|
|
|
|
- needing to type out the full flag name takes a long time, so I
|
|
would like to suggest adding auto-complete
|
|
- I use (osx, windows, linux) and would like support for (some
|
|
existing feature) to be extended to my platform
|
|
- the terminal output for a particular error case is confusing, and
|
|
I think it could be improved
|
|
|
|
## Solution description
|
|
|
|
A detailed description of what you want to happen.
|
|
|
|
## Describe alternatives you've considered
|
|
|
|
A clear and concise description of any alternative solutions or
|
|
features you've considered.
|