-
Notifications
You must be signed in to change notification settings - Fork 639
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
v2 migration: guides/test
to next
#1686
v2 migration: guides/test
to next
#1686
Conversation
✅ Deploy Preview for tauri-docs-starlight ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Will get #1670 worked through first then will take a look at this. |
guides/test
to nextguides/test
to next
created tsconfig alias changed from md to mdx
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i18n pages that had only 1 or 2 sentences translated were left behind.
[`mockipc()`]: https://tauri.app/v1/api/js/mocks#mockipc | ||
[`mockwindows()`]: https://tauri.app/v1/api/js/mocks#mockwindows | ||
[`clearmocks()`]: https://tauri.app/v1/api/js/mocks#clearmocks | ||
[vitest]: https://vitest.dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
links to v1 api docs, after a two seconds quick search I didn't find on v2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, asked in Discord https://discord.com/channels/616186924390023171/986184094050316358/1184092673133522996
Once we get some clarity on |
guides/test
to nextguides/test
to next
I raised this with the dev team. Let's go ahead and keep the links to v1 like we have for now. With that in mind is this one good to merge from your perspective? |
Updated some links and added TODO to update v2 links. I think it's ready. No need to place i18nReady right? |
Nope, no i18nReady on any of these since we're just doing a shift and not editing the content (wouldn't want to change it and then have someone translate things that will just be modified in the future). Once we get closer to v2 beta is probably when we'll do an overall check to make sure everything covered is relevant and correct for v2 (and note where not). |
What kind of changes does this PR include?
Description
Pages:
https://tauri.app/v1/guides/testing/mocking
https://tauri.app/v1/guides/testing/webdriver/introduction
https://tauri.app/v1/guides/testing/webdriver/example/setup
https://tauri.app/v1/guides/testing/webdriver/example/selenium
https://tauri.app/v1/guides/testing/webdriver/example/webdriverio
https://tauri.app/v1/guides/testing/webdriver/ci
TODO:
/example/setup.md