-
-
Notifications
You must be signed in to change notification settings - Fork 406
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
Advance RFC #0776 "Author Built-In Blueprints in TypeScript"
to Stage Recommended
#912
Conversation
@gitKrystan has volunteered to champion this going forward to make sure it moves. |
Per TS core meeting: Re updating guides, minimally we should add a TS page to the existing guides to cover this and other TS documentation that currently exists in multiple places. This will give people something to react to while we work on a more integrated TS/JS interactive guide. |
I've started a PR to the Guides for basic TS documentation. WIP PR here: ember-learn/guides-source#1960 |
For this particular RFC (which is about blueprint authoring), the remaining piece of docs needed is an update to https://cli.emberjs.com/release/advanced-use/blueprints/ The other TS guides content linked above is great and important for some of the other related TS RFCs, but not a blocker for this one. |
PR to add |
PR to add |
Advance #776 to the Recommended Stage
Summary
This pull request is advancing the RFC to the Recommended Stage.
An FCP is required before merging this PR to advance.
Recommended Stage Summary
The "Recommended" stage is the final milestone for an RFC. It provides a signal to the wider community to indicate that a feature has been put through its ecosystem paces and is ready to use.
To reach the "Recommended" stage, the following should be true:
If appropriate, the feature is integrated into the tutorial and the guides prose. API documentation is polished and updates are carried through to other areas of API docs that may not directly pertain to the feature.
If the proposal replaces an existing feature, the addon ecosystem has largely updated to work with both old and new features.
If the proposal updates or replaces an existing feature, high-quality codemods are available.
If needed, Ember debugging tools as well as popular IDE support have been updated to support the feature.
If the feature is part of a suite of features that were designed to work together for best ergonomics, the other features are also ready to be "Recommended".
Any criteria for "Recommended" for this proposal that were established in the Ready For Release stage have been met.
An FCP is required to enter this stage. Multiple RFCs may be moved as a batch into "Recommended" with the same PR.
Checklist to move to Recommended
Final Comment Period
label has been added to start the FCPCriteria for moving to Recommended (required)
A set of criteria for moving this RFC to the Recommended Stage, following release:
Update guides: This part according to:
https://github.com/cafreeman/rfcs/blob/typescript-blueprints/text/0776-typescript-blueprints.md#how-we-teach-this
isTypeScriptProject
on https://cli.emberjs.com/release/appendix/configuration/ Update configuration.md with isTypeScriptProject ember-learn/cli-guides#313Ember v4.12 is released as stable, as that release enables the feature flag by default