Repository navigation
docs: document the 22.0.0-rc.1 changes - #3835
Draft
armando-navarro wants to merge 1 commit into
Draft
armando-navarro wants to merge 1 commit into
armando-navarro wants to merge 1 commit into
Conversation
docs/zones.md says callback APIs hold the app unstable until an initial value, so a server render waits for data. angular#3827 makes a set of calls exceptions because their first callback may never come. Waiting on a callback that never comes would keep the app from ever becoming stable. List those calls in docs/zones.md, and point at onValue, object, list, listVal and fromRef with the value event as the calls that still make a server render wait. In docs/database.md, say the same under stateChanges, auditTrail and fromRef. Refs angular#3826
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
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.
Fixes #3834
This is the one docs PR for
22.0.0-rc.1. It stays a draft until the release.Why one docs PR per release
mainshows on GitHub as the current docs immediately, while the behavior it describes ships only in canaries until the next tagged release.How it works
22.0.0-rc.1that changes documented behavior does not carry the docs itself, and they get no PR of their own. They go here as one commit, added when the code PR is filed, and the code PR's description points here.22.0.0-rc.1tag, after the last code PR it describes, so the docs onmainand the published package change together.Commits so far
docs: say which wrapped calls do not hold the app unstable, for fix: stop twelve wrapped calls from holding the app unstable #3827: lists indocs/zones.mdthe wrapped calls that do not hold the app unstable, and adds one sentence each understateChanges,auditTrailandfromRefindocs/database.md.Checklist
yarn install,yarn testrun successfully?: not applicable, docs only.