Core Data: Rename types directory to entity-types
#39225
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When we introduced the types for the core entities in #38666 we used a directory named `types`. Unfortunately this meant that we can't create the customary file `src/types.ts` because of the name clash in module resolution. In this patch we're renaming the directory so that we can separately import `entity-types(/index.ts)` and also `types(.ts)` without the naming conflict.
dmsnell
added
[Type] Code Quality
|
Size Change: 0 B Total Size: 1.15 MB ℹ️ View Unchanged
|
dmsnell
added a commit
that referenced
this pull request
Mar 31, 2022
In this commit we're cleaning up type issues in the core-data package that prevent us from telling TypeScript to run on the package and all of its existing code, even the JS files. After these changes we should be able to do so and start converting more modules to TypeScript with less friction. This patch follows a series of other smaller updates: - #39212 - #39214 - #39225 - #39476 - #39477 - #39479 - #39480 - #39525 - #39526 - #39655 - #39656 - #39659 It was built in order to support ongoing work to add types to the `getEntityRecord` family of functions in #39025.
dmsnell
added a commit
that referenced
this pull request
Apr 1, 2022
In this commit we're cleaning up type issues in the core-data package that prevent us from telling TypeScript to run on the package and all of its existing code, even the JS files. After these changes we should be able to do so and start converting more modules to TypeScript with less friction. This patch follows a series of other smaller updates: - #39212 - #39214 - #39225 - #39476 - #39477 - #39479 - #39480 - #39525 - #39526 - #39655 - #39656 - #39659 It was built in order to support ongoing work to add types to the `getEntityRecord` family of functions in #39025.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #39211
Description
When we introduced the types for the core entities in #38666 we used a
directory named
types. Unfortunately this meant that we can't create thecustomary file
src/types.tsbecause of the name clash in module resolution.In this patch we're renaming the directory so that we can separately
import
entity-types(/index.ts)and alsotypes(.ts)without thenaming conflict.
Testing Instructions
Audit the types. As a type-only change this won't impact the built files.
Furthermore these types have been exported by
@wordpress/core-data; thatshouldn't change (verify please 😄 )
Types of changes
This is a type-only change and won't impact the build.
Checklist:
*.native.jsfiles for terms that need renaming or removal).