Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
aduth
left a comment
There was a problem hiding this comment.
I noticed this as well before and wondered if there might be some advantage is being intentionally narrow in what we want to support (e.g. explicitly not supporting *.scss imports). Probably not worth the deviation.
It did also prompt to wonder if the other types/ we have are still needed under types (specifically react.d.ts). Did you check that one?
|
Size Change: 0 B Total Size: 7.75 MB ℹ️ View Unchanged
|
|
Flaky tests detected in ddf45b1. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/24468372403
|
Good point. I think we can lift that up into a root typing so other packages can use it too. I'll follow up. |
What?
Follow-up to the shared TypeScript style import typings setup by switching
@wordpress/uito the existingstyle-importsdefinitions.Why?
@wordpress/uihad a package-local*.module.cssdeclaration that duplicated part of the shared typing already available intypings/style-imports.How?
style-importstopackages/ui/tsconfig.jsonpackages/ui/src/types/css-modules.d.tsdeclaration fileTesting Instructions
./node_modules/.bin/tsc -p packages/ui/tsconfig.json --pretty false.Use of AI Tools
Cursor was used to help prepare the change and draft this pull request. I reviewed the result before submitting it.