-
Notifications
You must be signed in to change notification settings - Fork 111
Where should docs live? #33
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
Comments
Wholeheartedly agree with Kent's suggestion. It would also need a PR against the docs to update the instructions now we've moved to scoped packages (+ maybe an example for cleanup-after-each?) |
Great! (Official docs have already been updated to fix the naming 😄 Source) So I'll submit a PR to remove docs from I've seen that React Testing Library, ReasonReact, and Native all have like sections with several pages: Wouldn't it be cool to have a similar structure for Vue? |
It would, happy for you to create this if you have the inclination |
Sure! I'll first update this repo README so we can close this up, and then think about a simple structure for docs in the official docs repo :) |
Please do! The other wrapper libs are a great starting point for structure. |
Hi! So, right now, there are two similar (but no exactly equal) versions of Vue Testing Library docs: in the
README
of this repo, and also inhttps://testing-library.com/vue
.Kent suggested here to keep the docs in the official website, and just point there from the repository README. How would you feel about that? Having a website seems more useful, as the docs could have several pages (intro, examples, setup, etc as other libraries) instead of having a single file.
I'll happily submit a PR for the README if you think that's the right approach!
The text was updated successfully, but these errors were encountered: