Skip to content
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: improve readability with additional subheaders #33168

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

pengooseDev
Copy link
Contributor

Description

Following #33138

  • Improved readability by adding subheaders in the "Make a change" section of the contribution guide.
  • Grouped TypeScript Type Generation and Write documentation for better accessibility.

Additionally, I wonder if moving the Linting section to the end of ## Make a change would improve the flow. (> link)
Since functional changes often impact types, placing TypeScript Type Generation and Write documentation together might enhance accessibility.

I would appreciate feedback. If there are any changes needed, I'm happy to make them. :)

This comment has been minimized.

This comment has been minimized.

Copy link
Contributor

@dgozman dgozman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the PR!

CONTRIBUTING.md Outdated
@@ -28,14 +30,10 @@ npx playwright install

Playwright is a multi-package repository that uses npm workspaces. For browser APIs, look at [`packages/playwright-core`](https://github.com/microsoft/playwright/blob/main/packages/playwright-core). For test runner, see [`packages/playwright`](https://github.com/microsoft/playwright/blob/main/packages/playwright).

Note that some files are generated by the build, so the watch process might override your changes if done in the wrong file. For example, TypeScript types for the API are generated from the [`docs/src`](https://github.com/microsoft/playwright/blob/main/docs/src).
### TypeScript Type Generation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it makes sense to put this after Write documentation. Or perhaps combine them? As you put it here, it seems like the most important part of making a change is to "generate types". In practice, you edit docs and everything just happens automatically 😄

This comment has been minimized.

Copy link
Contributor

Test results for "tests 1"

1 flaky ⚠️ [webkit-library] › library/browsercontext-add-cookies.spec.ts:429:3 › should allow unnamed cookies @webkit-ubuntu-22.04-node18

35085 passed, 618 skipped
✔️✔️✔️

Merge workflow run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants