test(tree): sandboxing demo#27649
Draft
yann-achard-MS wants to merge 30 commits into
Draft
Conversation
[How contribute to this repo](https://github.com/microsoft/FluidFramework/blob/main/CONTRIBUTING.md). [Guidelines for Pull Requests](https://github.com/microsoft/FluidFramework/wiki/PR-Guidelines#guidelines). The sections included below are suggestions for what you may want to include. Feel free to remove or alter parts of this template that do not offer value for your specific change. ## Description > A concise description of the changes (bug or feature) and their impact/motivation. > If this description is short enough to be used as the title, delete this section and just use the title. > For bug fixes, also include specifics of how to reproduce it / confirm it is fixed. > If this Pull Request should close/resolve any issues when merged, use [the special syntax for that](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) here. ## Breaking Changes > If this introduces a breaking change, please describe the impact and migration path for existing applications below. > See [Breaking-vs-Non-breaking-Changes](https://github.com/microsoft/FluidFramework/wiki/Breaking-vs-Non-breaking-Changes) for details. > If there are no breaking changes, delete this section. ## Reviewer Guidance The review process is outlined on [this wiki page](https://github.com/microsoft/FluidFramework/wiki/PR-Guidelines#guidelines). > List any specific things you want to get reviewer opinions on, and anything a reviewer would need to know to review this PR effectively. > Things you might want to include: > > - Questions about how to properly make automated tests for your changes. > - Questions about design choices you made. > - Descriptions of how to manually test the changes (and how much of that you have done). > - etc. > > If you have any questions in this section, consider making the PR a draft until all questions have been resolved.
[How contribute to this repo](https://github.com/microsoft/FluidFramework/blob/main/CONTRIBUTING.md). [Guidelines for Pull Requests](https://github.com/microsoft/FluidFramework/wiki/PR-Guidelines#guidelines). The sections included below are suggestions for what you may want to include. Feel free to remove or alter parts of this template that do not offer value for your specific change. ## Description > A concise description of the changes (bug or feature) and their impact/motivation. > If this description is short enough to be used as the title, delete this section and just use the title. > For bug fixes, also include specifics of how to reproduce it / confirm it is fixed. > If this Pull Request should close/resolve any issues when merged, use [the special syntax for that](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) here. ## Breaking Changes > If this introduces a breaking change, please describe the impact and migration path for existing applications below. > See [Breaking-vs-Non-breaking-Changes](https://github.com/microsoft/FluidFramework/wiki/Breaking-vs-Non-breaking-Changes) for details. > If there are no breaking changes, delete this section. ## Reviewer Guidance The review process is outlined on [this wiki page](https://github.com/microsoft/FluidFramework/wiki/PR-Guidelines#guidelines). > List any specific things you want to get reviewer opinions on, and anything a reviewer would need to know to review this PR effectively. > Things you might want to include: > > - Questions about how to properly make automated tests for your changes. > - Questions about design choices you made. > - Descriptions of how to manually test the changes (and how much of that you have done). > - etc. > > If you have any questions in this section, consider making the PR a draft until all questions have been resolved.
Contributor
|
Hi! Thank you for opening this PR. Want me to review it? Based on the diff (1052 lines, 10 files), I've queued these reviewers:
How this works
|
Contributor
|
🔗 No broken links found! ✅ Your attention to detail is admirable. linkcheck output |
Contributor
Bundle size comparisonBase commit: Notable changes
Per-bundle deltas
|
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
1 participant
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.
Description
Adds an example architecture for exposing a SharedTree view in a sandbox.
Breaking Changes
None