Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@BradBarnich
Copy link
Contributor

@BradBarnich BradBarnich commented Jul 17, 2023

Description

It seemed like a first step to ember-data shipping types was to use the ember-source types directly. This was a helpful to me when I was updating the @types/ember-data for ember-source types. Even if types are still shipped separately, this would make it easier to harmonize the shipped types to the internal types.

Notes for the release

not sure, seems like it is only visible internally

^ note from @runspired: this is correct. We intentionally do not ship types though this PR likely means we could ship types for @ember-data/tracking @ember-data/request @ember-data/request-utils @ember-data/rest and @ember-data/active-record starting as soon as 5.2. Would require a small cleanup pass.

@BradBarnich BradBarnich force-pushed the brad/use-ember-types branch from 3958f34 to 60d6dcf Compare July 17, 2023 16:05
@runspired runspired added 🏷️ chore This PR primarily refactors code or updates dependencies typescript For issues and PRs relating to typescript convertion 🎯 canary PR is targeting canary (default) labels Jul 18, 2023
Copy link
Contributor

@runspired runspired left a comment

Choose a reason for hiding this comment

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

I'd say this is 99% mergeable 💜. left a few comments to chat through first.

@esbanarango
Copy link
Contributor

What would be the next step once this PR is merged?

Is the end goal here to port the types of @ember-data/* into the actual releases of @ember-data, isn't it? I would like to help if more hands are needed.

@runspired runspired merged commit a815c9b into warp-drive-data:main Jul 23, 2023
@runspired
Copy link
Contributor

@esbanarango I think the next step is to port the DT types into the project, putting them into their respective packages within a folder named something like unstable-legacy-types or in <root>/unstable-legacy-types packages. We'll want to update the tsconfig to somehow ignore them (and give them their own tsconfig) and figure out a publishing strategy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🎯 canary PR is targeting canary (default) 🏷️ chore This PR primarily refactors code or updates dependencies typescript For issues and PRs relating to typescript convertion

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants