-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Testing: Include Prettier Config package in root type checking #21381
Conversation
Size Change: 0 B Total Size: 885 kB ℹ️ View Unchanged
|
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.
Looks correct 👍
We should probably add this step to the documentation. |
It's there (emphasis mine):
I'm open to suggestions for improving it. It's hard to walk the line between giving enough guidance and reproducing TypeScript documentation. The bullet list I added to #18838 may be better:
|
As noted by @sirreal , it's there. I merely failed to consider it. Which itself can be interesting observation. I've noted a few times in the past, but now formalized the idea into a task, the idea of trying to provide automated hints based on the interpreted intent of a pull request, in order to take away some of the manual (read: error-prone) steps of the process: https://github.com/WordPress/gutenberg/projects/24#card-36342702 |
Oh! I think I missed it because my brain instantly skims paragraphs and skips to where there are code blocks. |
Previously: #21362 (comment), #21053
This pull request seeks to include
@wordpress/prettier-config
in the root types-checking configuration. This was missed in #21053, and should be part of introduction of types checking for any package (see documentation).Testing Instructions:
Verify types build succeeds:
Verify the introduction of an error and subsequent re-run of the above would result in failure: