docs: declare Standalone APIs as stable#47754
Closed
AndrewKushnir wants to merge 1 commit intoangular:mainfrom
Closed
docs: declare Standalone APIs as stable#47754AndrewKushnir wants to merge 1 commit intoangular:mainfrom
AndrewKushnir wants to merge 1 commit intoangular:mainfrom
Conversation
AndrewKushnir
added
action: review
angular-robot
bot
added
the
feature
AndrewKushnir
force-pushed
the
standalone-apis-are-stable
branch
from
b110d3a to
c017960
Compare
AndrewKushnir
changed the title
angular-robot
bot
added
comp: docs
and removed
feature
AndrewKushnir
force-pushed
the
standalone-apis-are-stable
branch
from
c017960 to
1e74123
Compare
In v14, we've introduced core concepts to allow Components, Directives and Pipes to configure their dependencies without the need to use NgModules and without the need to be declared in an NgModule. The concepts and initial set of APIs were marked as "developer preview" to allow developers to use these APIs and share the feedback. Since v14, we've been reviewing the entire API surface of the framework and either updating existing APIs to support standalone or creating new APIs that allowed to use Router, HttpClient and other abstractions without NgMod ules. Based on the mentioned work to review and stabilize APIs and also based on the positive feedback from the commun ity, we are happy to announce that the Standalone APIs are promoted to stable! This commit updates vast majority of standalone-related APIs to drop the `@developerPreview` label, which effect ively documents then as stable. Two APIs that retained the `@developerPreview` annotations are: - withRequestsMadeViaParent (from `@angular/common/http`) - renderApplication (from `@angular/platform-server`) We plan to collect some additional feedback for the mentioned APIs and drop the `@developerPreview` annotation b efore the next major release. Co-Authored-By: Alex Rickabaugh <[email protected]> Co-Authored-By: Andrew Scott <[email protected]> Co-Authored-By: Dylan Hunn <[email protected]> Co-Authored-By: Jessica Janiuk <[email protected]> Co-Authored-By: JoostK <[email protected]> Co-Authored-By: Kristiyan Kostadinov <[email protected]> Co-Authored-By: Pawel Kozlowski <[email protected]>
AndrewKushnir
force-pushed
the
standalone-apis-are-stable
branch
from
1e74123 to
9f171c3
Compare
mgechev
approved these changes
Oct 12, 2022
alan-agius4
added
target: rc
alxhub
approved these changes
Oct 14, 2022
AndrewKushnir
added
action: merge
Contributor
Author
|
Caretaker note: this is a docs-only change, no presubmit is needed. I tried to force g3 status, but it doesn't seem to show up properly on the PR. This PR is ready for merge. |
Contributor
|
A feedback after testing standalone APIs by converting a full project: there is a NgModule which seems to have been forgotten and thus still need |
Contributor
|
This PR was merged into the repository by commit 0d65e1d. |
dylhunn
pushed a commit
that referenced
this pull request
Oct 17, 2022
In v14, we've introduced core concepts to allow Components, Directives and Pipes to configure their dependencies without the need to use NgModules and without the need to be declared in an NgModule. The concepts and initial set of APIs were marked as "developer preview" to allow developers to use these APIs and share the feedback. Since v14, we've been reviewing the entire API surface of the framework and either updating existing APIs to support standalone or creating new APIs that allowed to use Router, HttpClient and other abstractions without NgMod ules. Based on the mentioned work to review and stabilize APIs and also based on the positive feedback from the commun ity, we are happy to announce that the Standalone APIs are promoted to stable! This commit updates vast majority of standalone-related APIs to drop the `@developerPreview` label, which effect ively documents then as stable. Two APIs that retained the `@developerPreview` annotations are: - withRequestsMadeViaParent (from `@angular/common/http`) - renderApplication (from `@angular/platform-server`) We plan to collect some additional feedback for the mentioned APIs and drop the `@developerPreview` annotation b efore the next major release. Co-Authored-By: Alex Rickabaugh <[email protected]> Co-Authored-By: Andrew Scott <[email protected]> Co-Authored-By: Dylan Hunn <[email protected]> Co-Authored-By: Jessica Janiuk <[email protected]> Co-Authored-By: JoostK <[email protected]> Co-Authored-By: Kristiyan Kostadinov <[email protected]> Co-Authored-By: Pawel Kozlowski <[email protected]> PR Close #47754
Contributor
Author
@cyrilletuzi thanks for the feedback, I've created #47793 to capture this. Please let us know if you might be interested in creating a PR to add a new function. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
7 participants
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.
In v14, we've introduced core concepts to allow Components, Directives and Pipes to configure their dependencies without the need to use NgModules and without the need to be declared in an NgModule. The concepts and initial set of APIs were marked as "developer preview" to allow developers to use these APIs and share the feedback.
Since v14, we've been reviewing the entire API surface of the framework and either updating existing APIs to support standalone or creating new APIs that allowed to use Router, HttpClient and other abstractions without NgModules.
Based on the mentioned work to review and stabilize APIs and also based on the positive feedback from the community, we are happy to announce that the Standalone APIs are promoted to stable!
This commit updates vast majority of standalone-related APIs to drop the
@developerPreviewlabel, which effectively documents then as stable.Two APIs that retained the
@developerPreviewannotations are:@angular/common/http)@angular/platform-server)We plan to collect some additional feedback for the mentioned APIs and drop the
@developerPreviewannotation before the next major release.PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?