-
Notifications
You must be signed in to change notification settings - Fork 727
feat: add FAQ for svelte-testing-library #1268
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
Conversation
✅ Deploy Preview for testing-library ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi @yanick! Thanks for taking the time to open this one. |
True. But not everybody will think of searching the issues, let alone the closed issues, of the repo. Is there any downside to put that answer in the FAQ? I mean, it's not like it's currently overflowing with other Qs....
…On Sat, 8 Jul 2023, at 2:05 AM, Matan Borenkraout wrote:
Hi @yanick <https://github.com/yanick>! Thanks for taking the time to open this one.
I'm not sure this is worth an FAQ page since it's probably data that can be found in an issue.
I'm closing this, thanks again and sorry.
—
Reply to this email directly, view it on GitHub <#1268 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAE34R7FMUZ4KKXD3BWQMDXPD2A7ANCNFSM6AAAAAA2B5XXUI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
A simple search in google will probably raise the answer. The downside to putting something in the docs is that we need to maintain it and keep it updated, at the moment it's only one FAQ, but if we don't see a reason to create an FAQ besides that, I don't think we'd want to burden of maintaining it :) |
I would expect that the maintainer of svelte-testing-library has the job to keep the documention up-to-date. And that'd be me. But okay, FAQ in the project's README it is. 🤷 |
Sorry, I missed the part that you're maintaining it :) |
That was my expectation, yup. :-) |
@all-contributors please add @yanick for docs :) |
I've put up a pull request to add @yanick! 🎉 |
No description provided.