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

[QUEST] RFC 800: TypeScript Adoption Plan Implementation Tracking #20162

Open
15 of 26 tasks
Tracked by #868
chriskrycho opened this issue Aug 23, 2022 · 8 comments
Open
15 of 26 tasks
Tracked by #868

[QUEST] RFC 800: TypeScript Adoption Plan Implementation Tracking #20162

chriskrycho opened this issue Aug 23, 2022 · 8 comments
Labels
TypeScript Work on Ember’s types

Comments

@chriskrycho
Copy link
Contributor

chriskrycho commented Aug 23, 2022

RFC 0800 Tracking Issue

Implement RFC 0800: TypeScript Adoption Plan.

Enable TS blueprints

Publish types

We do not need to publish types for every package in Ember's dependencies—only for the packages which are part of its programmatic public APIs. An example of a dependency we don’t need to ship types with: ember-cli-dependency-checker is integrated into the classic Ember CLI build pipeline, but it doesn’t expose any APIs for users to call. The following list is comprised of the items in the default blueprints filtered for that criteria.

These items will be checked off if they have been "claimed"—please comment if you'd like to claim one! We will track their status via links to the issues/PRs which implement them.

Status: Last updated 2022/12/13, with the dependencies from the app and v1 addon blueprints.

Footnotes

  1. Debatably, anyway: we could work on dropping this instead, and its public API usage is intended to be minimal; but right now it is a public API.

@chriskrycho chriskrycho added the TypeScript Work on Ember’s types label Aug 23, 2022
@chriskrycho chriskrycho changed the title [draft] RFC 800: TypeScript Adoption Plan Implementation Tracking [draft] [QUEST] RFC 800: TypeScript Adoption Plan Implementation Tracking Sep 1, 2022
@chriskrycho chriskrycho changed the title [draft] [QUEST] RFC 800: TypeScript Adoption Plan Implementation Tracking [QUEST] RFC 800: TypeScript Adoption Plan Implementation Tracking Dec 13, 2022
@bertdeblock
Copy link
Member

FYI, the ember-cli-sri repo is archived.

@bertdeblock
Copy link
Member

@chriskrycho Seems like a part is missing from the ember-fetch entry in the list above?

@chriskrycho
Copy link
Contributor Author

Oh, good catches on both points. Updating!

@ijlee2
Copy link
Member

ijlee2 commented Dec 16, 2022

@chriskrycho @bertdeblock I'd like to help out with ember-welcome-page.

I think we need to first update the repo (CI, dependencies, and minimum support for Node & Ember), before we introduce TypeScript, though. This would help with future maintenance.

Is it okay if I temporarily own the project and make a few pull requests to keep the project up-to-date and easy to maintain?

@chriskrycho
Copy link
Contributor Author

Please do! I'll mark is at "taken" here and am happy to help with any TS work there.

@ijlee2
Copy link
Member

ijlee2 commented Dec 16, 2022

@chriskrycho Thanks!

@kategengler
Copy link
Member

@emberjs/typescript-core Can this be closed?

@gitKrystan
Copy link
Contributor

I think we've completed the high-priority items on this list but not everything. Checking in with @wagenet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TypeScript Work on Ember’s types
Projects
None yet
Development

No branches or pull requests

5 participants