-
Notifications
You must be signed in to change notification settings - Fork 532
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.
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
Automation: main-next integrate #16417
Merged
Merged
Conversation
This file contains 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
## Description This emits a "revertible" event when a change is made that can be undone or redone on a SharedTreeView. This allows consumers to listen to the event in order to manage the sequencing of calls to undo/redo on a SharedTree vs other DDSes. ## Reviewer Guidance The review process is outlined on [this wiki page](https://github.com/microsoft/FluidFramework/wiki/PR-Guidelines#guidelines). --------- Co-authored-by: Noah Encke <78610362+noencke@users.noreply.github.com>
## Description sequence-change-family is an example change family (compare to the production modular-change-family) which was used to as part of bootstrapping and prototyping. Since its very similar to but not sharing code with sequence fields in modular change family, maintaining it has some costs. Additionally, it does not serve as a great change family example since it implements somewhat complex policies. A simple last write wins optional field changeset might make a better example, but for now we can live without any alternative change family implementations. Thus, this deletes sequence-change-family.
Bumped build-tools from 0.21.0 to 0.22.0.
The `exactDepType` flag in flub bump was deprecated and replaced by interdependencyRange. Update to use it.
Promise.reject should not generally be used, and almost never returned. This PR replaces `return Promise.reject(...)` with `throw ...` which is semantically equivalent, but takes less code, and more accurately matches intent. --------- Co-authored-by: Tony Murphy <anthonm@microsoft.com>
github-actions
bot
added
area: build
Build related issues
area: dds
Issues related to distributed data structures
area: dds: propertydds
area: dds: tree
area: driver
Driver related issues
area: odsp-driver
area: server
Server related issues (routerlicious)
public api change
Changes to a public API
base: next
PRs targeted against next branch
labels
Jul 18, 2023
⯅ @fluid-example/bundle-size-tests: +97 Bytes
Baseline commit: d00cc1f |
sonalideshpandemsft
approved these changes
Jul 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: build
Build related issues
area: dds: propertydds
area: dds: tree
area: dds
Issues related to distributed data structures
area: driver
Driver related issues
area: odsp-driver
area: server
Server related issues (routerlicious)
base: next
PRs targeted against next branch
do-not-squash-merge
main-next-integrate
public api change
Changes to a public API
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.
main-next integrate PR
The aim of this pull request is to sync main and next branch. If this PR is assigned to you, you need to do the following:
git checkout main-next-9fbaa3b
-- check out the PR branch.