Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: Minor adjustments to release notes #23464

Merged
merged 1 commit into from
Jan 6, 2025
Merged

build: Minor adjustments to release notes #23464

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .changeset/moody-pandas-fall.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@
"section": tree
---

New alpha APIs for schema evolution

There are now `@alpha` APIs for schema evolution which support adding optional fields to object node types without a staged rollout.

SharedTree has many safety checks in place to ensure applications understand the format of documents they must support.
Expand Down
6 changes: 4 additions & 2 deletions RELEASE_NOTES/2.13.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,14 @@
## Contents

- [🌳 SharedTree DDS Changes](#-sharedtree-dds-changes)
- [There are now `@alpha` APIs for schema evolution which support adding optional fields to object node types without a staged rollout. (#23362)](#there-are-now-alpha-apis-for-schema-evolution-which-support-adding-optional-fields-to-object-node-types-without-a-staged-rollout-23362)
- [New alpha APIs for schema evolution (#23362)](#new-alpha-apis-for-schema-evolution-23362)
- [Metadata can be associated with Node Schema (#23321)](#metadata-can-be-associated-with-node-schema-23321)

## 🌳 SharedTree DDS Changes

### There are now `@alpha` APIs for schema evolution which support adding optional fields to object node types without a staged rollout. ([#23362](https://github.com/microsoft/FluidFramework/issues/23362))
### New alpha APIs for schema evolution ([#23362](https://github.com/microsoft/FluidFramework/issues/23362))

There are now `@alpha` APIs for schema evolution which support adding optional fields to object node types without a staged rollout.

SharedTree has many safety checks in place to ensure applications understand the format of documents they must support. One of these checks verifies that the view schema (defined in application's code) aligns with the document schema (determined by the document data at rest). This helps to ensure that clients running incompatible versions of the application's code don't collaborate at the same time on some document, which could cause data loss or disrupt application invariants. One general solution application authors can perform is to stage the rollout of a feature which changes document schema into multiple phases:

Expand Down
Loading