Repository navigation
Conversation
alxhub
added
action: merge
Member
Author
IgorMinar
approved these changes
May 23, 2019
IgorMinar
left a comment
IgorMinar
left a comment
Contributor
There was a problem hiding this comment.
can you please list the deprecated symbols in the deprecation's guide index table https://github.com/angular/angular/blob/master/aio/content/guide/deprecations.md#index
thanks!
Member
Author
|
@IgorMinar done! |
Splaktar
reviewed
May 23, 2019
Splaktar
left a comment
Splaktar
left a comment
Contributor
There was a problem hiding this comment.
Are we sure that the platform-webworker* API will be removed in version 10? do we need to specify that in the multiple comments? or should that just be reflected in the deprecation guide?
DEPRECATION: Angular previously has supported an integration with the Web Tracing Framework (WTF) for performance testing of Angular applications. This integration has not been maintained and likely does not work for the majority of Angular applications today. As a result, we are deprecating the integration in Angular version 8. This deprecation covers the following public APIs: * `WtfScopeFn` * `wtfCreateScope` * `wtfStartTimeRange` * `wtfEndTimeRange` * `wtfLeave` FW-1338 #resolve
DEPRECATION: platform-webworker has been around since the initial release of Angular version 2. It began as an experiment to leverage Angular's rendering architecture and try something different: to run an entire web application in a web worker. We've learned a lot from this experiment, and have come to the conclusion that pushing entire applications to run in a web worker is not a recipe for success for most applications. This is due to a number of unresolved issues, including: * Poor or non-existent support for web worker APIs in web crawlers/indexers. * Poor support in build and bundling tooling. As a result, as of Angular version 8, we are deprecating the `platform-webworker` APIs in Angular. This consists of both NPM packages, `@angular/platform-webworker` and `@angular/platform-webworker-dynamic`. Going forward, we will focus our efforts related to web workers around their primary use case of offloading CPU-intensive but not critical work. FW-1339 #resolve
|
You can preview 8699ddb at https://pr30642-8699ddb.ngbuilds.io/. |
jasonaden
pushed a commit
that referenced
this pull request
May 23, 2019
DEPRECATION: platform-webworker has been around since the initial release of Angular version 2. It began as an experiment to leverage Angular's rendering architecture and try something different: to run an entire web application in a web worker. We've learned a lot from this experiment, and have come to the conclusion that pushing entire applications to run in a web worker is not a recipe for success for most applications. This is due to a number of unresolved issues, including: * Poor or non-existent support for web worker APIs in web crawlers/indexers. * Poor support in build and bundling tooling. As a result, as of Angular version 8, we are deprecating the `platform-webworker` APIs in Angular. This consists of both NPM packages, `@angular/platform-webworker` and `@angular/platform-webworker-dynamic`. Going forward, we will focus our efforts related to web workers around their primary use case of offloading CPU-intensive but not critical work. FW-1339 #resolve PR Close #30642
jasonaden
pushed a commit
that referenced
this pull request
May 23, 2019
#30642) DEPRECATION: Angular previously has supported an integration with the Web Tracing Framework (WTF) for performance testing of Angular applications. This integration has not been maintained and likely does not work for the majority of Angular applications today. As a result, we are deprecating the integration in Angular version 8. This deprecation covers the following public APIs: * `WtfScopeFn` * `wtfCreateScope` * `wtfStartTimeRange` * `wtfEndTimeRange` * `wtfLeave` FW-1338 #resolve PR Close #30642
jasonaden
pushed a commit
that referenced
this pull request
May 23, 2019
DEPRECATION: platform-webworker has been around since the initial release of Angular version 2. It began as an experiment to leverage Angular's rendering architecture and try something different: to run an entire web application in a web worker. We've learned a lot from this experiment, and have come to the conclusion that pushing entire applications to run in a web worker is not a recipe for success for most applications. This is due to a number of unresolved issues, including: * Poor or non-existent support for web worker APIs in web crawlers/indexers. * Poor support in build and bundling tooling. As a result, as of Angular version 8, we are deprecating the `platform-webworker` APIs in Angular. This consists of both NPM packages, `@angular/platform-webworker` and `@angular/platform-webworker-dynamic`. Going forward, we will focus our efforts related to web workers around their primary use case of offloading CPU-intensive but not critical work. FW-1339 #resolve PR Close #30642
Contributor
|
I got pulled away for a bit after the AIO preview was posted, so I didn't get a chance to look at it. We now have duplicated anchors and The one from PR #30598: The one from this PR: The |
4 of 14 tasks
|
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.
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.
Two deprecations for 8.0.