-
Notifications
You must be signed in to change notification settings - Fork 28.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test: Issue Reporter Command improvements #203094
Comments
I don't think this replaces the previous IssueDataProvider. The IssueDataProvider was invoked when you opened the Issue Reporter and chose the extension. This, on the other hand, needs to be invoked by an extension. With only this command, as a user, I can still open the Issue reporter, go to the extension with the issue and not see any of the auto-filled content. We need a solution that covers both of these scenarios (invoked by extension, and by issue reporter) |
Continuation of #196324
Complexity: 4
Create Issue
Overview
Added improvements to the Issue Reporter Command. Instead of an API, we now are testing a basic version of the
openIssueReporter
command that does virtually the same thing as the API.The following is the structure of what an example call to
openIssueReporter
could look like.note:
template
,data
, anduri
are all expected to bestring
typed.The general idea is that from anywhere, you could run this command and give it some parameters, mainly things like a template (which will go to the body), data (which if contributed, will add a data field), or a uri (which if contributed, will replace the repo url).
To test
Help: Report Issue
from the command palette) is not broken.Some things to make sure:
Thanks!
The text was updated successfully, but these errors were encountered: