50 lines
1.8 KiB
Markdown
50 lines
1.8 KiB
Markdown
---
|
|
name: Feature request
|
|
about: Follow the instructions carefully on the next page.
|
|
title: ''
|
|
labels: 1 backlog, enhancement
|
|
assignees: ryanheise
|
|
|
|
---
|
|
|
|
<!--
|
|
|
|
Note: Issues that don't follow these instructions will be closed,
|
|
therefore please read them carefully.
|
|
|
|
1. A prerequisite before requesting a feature is that you familiarise
|
|
yourself with the existing features by reading the API
|
|
documentation.
|
|
|
|
2. If it is unclear from the documentation whether an existing feature
|
|
is the one you want, this is a shortcoming of the documentation. In
|
|
this case, please submit a documentation request instead.
|
|
|
|
3. Do not use this form for asking questions. My goal is to provide
|
|
good documentation that answers your questions, and if the
|
|
documentation isn't doing its job, please submit a documentation
|
|
request to help me to improve it. Remember that the purpose of this
|
|
GitHub issues page is for plugin development and not for support
|
|
(community support is available via StackOverflow and Gitter).
|
|
|
|
4. You must complete at least the first 3 sections below. Leave the
|
|
section headings intact, and insert your answers below each heading.
|
|
|
|
THANK YOU :-D
|
|
|
|
|
|
-->
|
|
|
|
|
|
**Is your feature request related to a problem? Please describe.**
|
|
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
|
|
|
|
**Describe the solution you'd like**
|
|
<!-- A clear and concise 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. -->
|
|
|
|
**Additional context**
|
|
<!-- Add any other context or screenshots about the feature request here. -->
|