chore: use discussions for feature requests
This commit is contained in:
parent
3cdb93941d
commit
b21c4fa881
4 changed files with 12 additions and 14 deletions
2
.github/ISSUE_TEMPLATE/bug_report.md
vendored
2
.github/ISSUE_TEMPLATE/bug_report.md
vendored
|
|
@ -16,7 +16,7 @@ Describe what happens instead. Best via a live code reproduction.
|
|||
To create one click the link below and edit away.
|
||||
Once the error is reproduced fork/safe and link it.
|
||||
|
||||
https://webcomponents.dev/edit/kpZmz1CJN580OaXsk56f?sv=1&pm=1
|
||||
https://webcomponents.dev/edit/kpZmz1CJN580OaXsk56f?pm=1
|
||||
|
||||
## Additional context
|
||||
|
||||
|
|
|
|||
14
.github/ISSUE_TEMPLATE/feature_request.md
vendored
14
.github/ISSUE_TEMPLATE/feature_request.md
vendored
|
|
@ -1,19 +1,9 @@
|
|||
---
|
||||
name: Feature Request
|
||||
about: You have an idea about an additional feature
|
||||
title: '[Feature Request] ...'
|
||||
title: '[Feature Request] please use the discussions tab'
|
||||
labels: ''
|
||||
assignees: ''
|
||||
---
|
||||
|
||||
## Idea
|
||||
|
||||
By adding `my-flag` we can solve ...
|
||||
|
||||
## Straw Man Proposal
|
||||
|
||||
The api could look like this
|
||||
|
||||
```js
|
||||
<my-el my-flag="option"></my-el>
|
||||
```
|
||||
Please use [discussions](https://github.com/ing-bank/lion/discussions/new) for new feature requests.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ Check out ways to contribute to Lion Web Components:
|
|||
|
||||
## Feature requests
|
||||
|
||||
When you have an idea on how we could improve, please check our [closed issues](https://github.com/ing-bank/lion/issues?q=is%3Aissue+is%3Aclosed+label%3Aenhancement) to see if there are similar ideas. If there are none, please [submit](https://github.com/ing-bank/lion/issues/new/choose) your feature request as an issue. Add a clear description of what you expect from the improvement and what the use case is. The issue will be closed and the community can add 👍 reactions to [vote and show interest](https://github.com/ing-bank/lion/issues?q=label%3A%22votes+needed%22+sort%3Areactions-%2B1-desc). When the feature gets picked up, the issue can be reopened.
|
||||
When you have an idea on how we could improve, please check our [discussions](https://github.com/ing-bank/lion/discussions) to see if there are similar ideas or feature requests. If there are none, please [start](https://github.com/ing-bank/lion/discussions/new) your feature request as a new discussion topic. Add the title `[Feature Request] My awesome feature` and a description of what you expect from the improvement and what the use case is.
|
||||
|
||||
## Existing components: we love pull requests ♥
|
||||
|
||||
|
|
|
|||
|
|
@ -33,6 +33,14 @@ Additionally imports like `import '@lion/form/lion-form.js'` need to be transfor
|
|||
> Note: These demos may look a little bland but that is on purpose. They only come with functional stylings.
|
||||
> This makes sense as the main use case is to extend those components and if you do you do not want to override existing stylings.
|
||||
|
||||
## Issues
|
||||
|
||||
If you encouter an issue with any of the packages we are offering please open a [new bug issue](https://github.com/ing-bank/lion/issues/new?assignees=&labels=&template=bug_report.md&title=). Be sure to include a description of the expected and the current behavior - additional adding a [reproduction](https://webcomponents.dev/edit/kpZmz1CJN580OaXsk56f?pm=1) always helps.
|
||||
|
||||
## Feature requests
|
||||
|
||||
When you have an idea on how we could improve, please check our [discussions](https://github.com/ing-bank/lion/discussions) to see if there are similar ideas or feature requests. If there are none, please [start](https://github.com/ing-bank/lion/discussions/new) your feature request as a new discussion topic. Add the title `[Feature Request] My awesome feature` and a description of what you expect from the improvement and what the use case is.
|
||||
|
||||
## Content
|
||||
|
||||
Lion web components is logically organized in groups of systems.
|
||||
|
|
|
|||
Loading…
Reference in a new issue