This repository was archived by the owner on Apr 12, 2024. It is now read-only.
docs(faq): document the AngularJS/jqLite deprecation strategy #15819
Conversation
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
Narretz
suggested changes
Mar 15, 2017
docs/content/misc/faq.ngdoc
Outdated
| @@ -130,6 +130,15 @@ AngularJS 1.3 only supports jQuery 2.1 or above. jQuery 1.7 and newer might work | |||
| but we don't guarantee that. | |||
|
|
|||
|
|
|||
| ### When will the deprecated features be removed from the library? | |||
There was a problem hiding this comment.
When are will the deprecated features be ...
docs/content/misc/faq.ngdoc
Outdated
| @@ -130,6 +130,15 @@ AngularJS 1.3 only supports jQuery 2.1 or above. jQuery 1.7 and newer might work | |||
| but we don't guarantee that. | |||
|
|
|||
|
|
|||
| ### When will the deprecated features be removed from the library? | |||
| Most of the time we remove a deprecated feature in a next minor bump. For example, the `preAssignBindingsEnabled` | |||
docs/content/misc/faq.ngdoc
Outdated
| @@ -130,6 +130,15 @@ AngularJS 1.3 only supports jQuery 2.1 or above. jQuery 1.7 and newer might work | |||
| but we don't guarantee that. | |||
|
|
|||
|
|
|||
| ### When will the deprecated features be removed from the library? | |||
| Most of the time we remove a deprecated feature in a next minor bump. For example, the `preAssignBindingsEnabled` | |||
| `$compileProvider` method was defined in AngularJS `1.5.10`, deprecated in `1.6` and will be removed in `1.7`. | |||
There was a problem hiding this comment.
We'll have to change this when 1.7.0 is released.
There was a problem hiding this comment.
Hmm, maybe it'd be better to put sth else here, preferably something where we adhered to this strategy. :)
Makes sense. |
|
@Narretz PR updated, PTAL. I amended the commit as the diff wouldn't tell much anyway when the whole section is moved. |
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Docs update.
What is the current behavior? (You can also link to an open issue here)
The deprecation strategy is not specified.
What is the new behavior (if this is a feature change)?
The deprecation strategy is specified.
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements
Other information:
Fixes #15282