-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Update README #338
Comments
In my opinion, since consumers of the extension are developers, there isn't a need to go into so much detail to create new sections for simple things like running a test, or things developers are already familiar with (such as managing breakpoints). I believe the current format can be extended to further explain certain things such as test filters, better way to display the configuration. |
There a lot of developers who don't have enough knowledge to even install Vitest. Explaining how breakpoints work or how to navigate through the interface will go a long way in helping junior developers work with the extension efficiently. There are a lot of nuances to how tests are displayed (tree view, file view, "test results" tab, switching between different test runs and so on)
This should help developers understand why the extension doesn't work for them. For example, this explains why the extension doesn't work if you don't have a config file at all (which, granted, we should support in the future) or why you might see several test profiles when clicking on "Continues Run" or trying to filter tests. This should also help contributors understand how the extension works on a higher level before diving in the code. |
Clear and concise description of the problem
Our current README doesn't provide enough information on how to work with the extension.
Suggested solution
Add several new sections:
debugger
statement@open
)I would also like to rewrite the introduction section:
It should look something like this:
All screenshots need to use the same project that should be pushed to the repository so we can reshoot it if needed. All screenshots need to have the same VS Code theme. Ideally, screenshots should have a border with a shadow (like on Mac OS) - this is just my preference 😄
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: