-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
docs(intro-section): fix links #17241
Conversation
docs/src/test-reporters-js.md
Outdated
}; | ||
|
||
module.exports = config; | ||
``` | ||
|
||
```js tab=js-ts | ||
// playwright.config.ts | ||
import type { PlaywrightTestConfig } from '@playwright/test'; | ||
import type { PlaywrightTestConfig } from "@playwright/test"; |
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.
There is a lot of formatting in this PR, but I think most of it does not fit Playwright coding conventions. The codebase and most of the examples are using single quotes, for example.
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.
Thanks for catching it. My formatter had different settings. Fixed the docs.
docs/src/test-reporters-js.md
Outdated
test("embed attachments, including its content, on the JUnit report", async ({}, testInfo) => { | ||
const file = testInfo.outputPath("evidence1.txt"); | ||
require("fs").writeFileSync(file, "hello", "utf8"); | ||
await testInfo.attach("evidence1.txt", { |
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.
Maybe the more compact code style that was originally used is better for docs ? 🤔
await testInfo.attach('evidence1.txt', { path: file, contentType: 'text/plain' });
Great work guys. Thanks :) |
Fix the link to getting started sections.
cc - @debs-obrien