Repository navigation
docs(forms): remove remaining experimental framing from Signal Forms docs - #71116
Merged
Merged
Conversation
…docs Signal Forms was graduated to public API in v22, but the tutorial's last step still calls it experimental and the overview still suggests it lacks production stability guarantees.
JeanMeche
approved these changes
Oct 1, 2026
Contributor
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
Signal Forms APIs were graduated to public API in v22 (#68581), and the experimental framing was subsequently removed from the package documentation in #68769 and #69305.
There are still two places in
adevthat describe Signal Forms as not stable:What is the new behavior?
The tutorial still points readers to the official documentation, but no longer describes Signal Forms as experimental.
The overview still recommends Reactive Forms for existing Reactive Forms applications, but no longer suggests that Signal Forms lacks production stability guarantees.
Does this PR introduce a breaking change?
Other information
Docs-only change in
adev/src/content/tutorials/signal-forms/steps/6-next-steps/README.mdandadev/src/content/guide/forms/signals/overview.md.