Updated the warning for the EditorModel notifications article to be more explicit #6207
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
The EditorModel notifications article currently explains that the
Sending***Notificationnotifications still exist. They have been explicitly removed in V14, because their functionality is a client-side responsibility moving forward.This PR adds a warning to the top of the article (and removes the current warning in the middle of the article), to let people know that the entire article is out of date.
Type of suggestion
Product & version (if relevant)
V14
Deadline (if relevant)
Whenever possible. Not super urgent.