chore: upgrade issues templates #11
Conversation
| validations: | ||
| required: true | ||
|
|
||
| - type: dropdown |
There was a problem hiding this comment.
Am I right that the user has to specify a runtime? The issue might not even related to it, but rather the supabase dashboard or some api repository.
There was a problem hiding this comment.
You're right, i tried to keep the templates that were there, so that only the style changes, and potentially add other information (such as the choice of runtime).
Do you think we should modify these new templates so that they are more representative of Supabase's work? Including, for example, a dropdown to choose what the issue is about (supabase-js, supabase-flutter....)?
There was a problem hiding this comment.
It depends on where the template gets applied to. In the flutter repos, we currently have our own issue templates. All flutter related issues should be collected there and not in the supabase/supabase repo. So I don't think it makes sense to add a client library dropdown. I think the template here should be very general. Repository specific information should be specified in a template per repository. What do you think?
There was a problem hiding this comment.
Sounds good, pushing an update asap
| validations: | ||
| required: false | ||
|
|
||
| - type: input |
There was a problem hiding this comment.
Same as below. Not all issues have to do with supabase-js
What kind of change does this PR
This pull request upgrade issues templates.
What is the current behavior?
The current system works. At the same time, users can change the information as they wish, and potentially leave out some of the requested information. This is not possible with this new template system.
It also adds a
triagelabel interaction to make the issue triage easier. This is another idea, and can be removed if you prefer.What is the new behavior?
Before
After
Additional context
Please let me know if you think it's a good idea, and if so, if i should do the same for other repositories.