Repository navigation
docs(compat): state the compatibility API's support status - #3810
Open
armando-navarro wants to merge 1 commit into
Open
armando-navarro wants to merge 1 commit into
armando-navarro wants to merge 1 commit into
Conversation
docs/compat.md had no statement of whether @angular/fire/compat is supported, and the v7 upgrade guide still told readers to stop at the compatibility API because the modular API was not feature complete, a sentence written for the 7.0 release. The new section records the decision for 22: the compatibility API is supported and kept working, its specs run in the same suite, it receives bug fixes and no new features, and no removal is planned. The v7 guide line now points at that section.
KingDarBoja
approved these changes
Oct 24, 2026
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.
Checklist
yarn install,yarn testrun successfully? Not run, the change is two Markdown files.npm run lintpassed.Description
docs/compat.mdnever said whether@angular/fire/compatis supported, and the v7 upgrade guide still told readers to stop at the compatibility API because the modular API "isn't feature complete", a sentence from the 7.0 release. #3336 asked for a direct answer in 2023 and never got one. This writes the answer down.Changes
docs/compat.mdgets a "Support status" section: the compatibility API is supported and kept working on every Angular and Firebase version AngularFire supports, its specs run in the same test suite as the modular API, it receives bug fixes and no new features, and there is no planned removal date. Readers who depend on it can keep upgrading without migrating.docs/version-7-upgrade.md: the bolded line becomes "You can stop here if the compatibility API covers your needs.", followed by the support summary and a link to the new section.Fixes #3336