| 1 | ---
|
| 2 | name: Feature request
|
| 3 | about: Suggest an idea for this project
|
| 4 | title: ''
|
| 5 | labels: ''
|
| 6 | assignees: ''
|
| 7 |
|
| 8 | ---
|
| 9 |
|
| 10 | **Description of new feature**
|
| 11 |
|
| 12 | _What should the new feature do? For visual features, include an image/mockup of the expected output._
|
| 13 |
|
| 14 |
|
| 15 |
|
| 16 | **Motivation for new feature**
|
| 17 |
|
| 18 | _Describe your use case for this new feature._
|
| 19 |
|
| 20 |
|
| 21 |
|
| 22 | **For reviewers**
|
| 23 |
|
| 24 | _Reviewers should ensure that the following tasks are carried out for incorporated issues:_
|
| 25 |
|
| 26 | - [ ] Ensure that the reporter has adequately described their idea. If not, elicit more information about the use case. You should iteratively build a spec together.
|
| 27 | - [ ] Ensure that the issue is a good fit for the core library. Some things are best done in extensions (e.g. UI-related features that aren't style-related). Some things are best done by app authors themselves -- instead of in Cytoscape libraries.
|
| 28 | - [ ] The issue has been associated with a corresponding [milestone](https://github.com/cytoscape/cytoscape.js/milestones).
|
| 29 | - [ ] The commits have been incorporated into the `unstable` branch via pull request. The corresponding pull request is cross-referenced.
|
| 30 |
|