Fix "Use case" -> "Possible solution" field name in feature request template

feature_request.yaml had two "use case" fields
This commit is contained in:
Vladimir Sitnikov 2022-09-24 19:22:44 +03:00 committed by GitHub
parent 383cbaa544
commit 1f588f6075
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -18,7 +18,7 @@ body:
- type: textarea
id: solution
attributes:
label: Use case
label: Possible solution
description: |
Please describe a possible solution you'd like to see in jOOQ, ideally with example code.
Please note, it's not always easy to describe a good solution. Describing the use-case above is much more important to us.