## Description
Deletes some packages from experimental/PropertyDDS.
The DDS and its dependencies are kept, but the rest of its packages are
not.
Delete the following published experimental packages:
- @fluid-experimental/property-shared-tree-interop
- @fluid-experimental/property-binder
- @fluid-experimental/property-proxy
- @fluid-experimental/property-inspector-table
Delete the following private packages:
- @fluid-example/property-inspector
- @fluid-example/schemas
Changes made by deleting the packages, then running:
```
pnpm i --no-frozen-lockfile
pnpm layer-check --md .
```
and manually adding a changeset.
## Breaking Changes
These packages will no longer be published:
- @fluid-experimental/property-shared-tree-interop
- @fluid-experimental/property-binder
- @fluid-experimental/property-proxy
- @fluid-experimental/property-inspector-table
## Description
This removes the `@fluid-example/bubblebench-shared-tree-flex-tree`
package from PACKAGES.md, which was not done when originally removing
the package in #22004
This is an example that demonstrates the deprecated 'table-document'
DataObject.
We maintain 'table-document' to support migrating legacy document.
The Table-View sample is unused, has no tests, and should be removed.
## Description
> This resolver plays a crucial role in converting URLs from OneNote and
Office.com for the Fetch tool, which is essential for retrieving
snapshots for analysis when needed. Therefore, it's not feasible to
eliminate this resolver.
Renames the packages from the `@fluid-experimental` namespace to the
`@fluidframework` namespace in preparation for the upcoming 2.0 release
candidate.
Note that while only the `devtools` package will be advertised publicly,
it depends on `devtools-core`, so both really need to move.
Additionally, while we don't publish `devtools-view`, we do use it in
"production" as a part of our browser extension, so it also really
doesn't belong in `@fluid-experimental` anymore. This PR moves it to
`@fluid-internal`.
This is one in a series of PRs to rename current packages that are only
published to our internal npm feeds to use the @fluid-private scope.
This PR covers the following fluid-internal packages:
- test-dds-utils
- test-loader-utils
This is one in a series of PRs to rename current packages that are only
published to our internal npm feeds to use the \@fluid-private scope.
This PR covers the following fluid-internal packages:
- test-version-utils
- test-pairwise-generator
This is one in a series of PRs to rename current packages that are only
published to our internal npm feeds to use the @fluid-private scope.
This PR covers the following fluid-internal packages:
- stochastic-test-utils
- test-drivers
This is one in a series of PRs to rename current packages that are only
published to our internal npm feeds to use the @fluid-private scope.
This PR covers the following fluid-internal packages:
- @fluid-internal/test-end-to-end-tests
In #16856 we copied some functions out of common-utils. This PR updates
the client release group to use the new client-only packages instead of
common-utils. **common-utils is no longer used in the client release
group.**
## Description
This work was started and abandoned in #13100.
The goal/requirement here is to allow each stage of ScenarioRunner to
pass along certain parameters to the next stage. This can enable us to
create specific scenarios that rely on multiple things happening with 1
AzureClient instance by using configs rather than building an entire
Runner for each scenario.
For example, a while back we ran into an issue where if 1 AzureClient
instance was used to load 2 different documents, the 2nd document would
fail to load due to cache pollution (see #12060). To repro this
currently with ScenarioRunner, we would have to create an entire new
Runner that spawns 2 documents from 1 AzureClient. Ideally, we could do
like
1. stage: azure-client
- passes: client
2. stage: doc-creator
- consumes: client
- passes: docId
3. stage: doc-loader
- consumes: client, docId
4. stage: doc-creator
- consumes: client
- passes: docId
5. stage: doc-loader
- consumes: client, docId
This PR doesn't actually quite get us to this specific repro yet, but
it's 1 step closer.
ScenarioRunner already has `out` env set-up going on, but it currently
always runs in multiple processes. When running in multiple processes,
you can't share an AzureClient instance. This PR just allows tests to be
run with 1 process, rather than multiple processes so that complex
objects can be shared between stages.
## Breaking Changes
- Changes the `IRunner` interface to expect both `run` and `runSync`
(previously just `run`).
- Makes `AzureClientConfig` from each `Runner` shared as
`AzureClientConnectionConfig` from `interfaces.ts`. This is different
from `AzureClientConfig` in `utils.ts`, though many of the properties
mean the same things.
## Reviewer Guidance
Overall, this PR does 3 things:
1. Moves `execRun` from `*RunnerClient.ts` files into each `*Runner.ts`
file as a `public static` class property of the `Runner`. This allows
both `run` and `runSync` to utilize the business logic of the Runner,
and also narrows the `*RunnerClient` scope to parsing command line args
to build a config.
2. Adds a `runSync` method to each `Runner` that operates similarly to
`run`, but using 1 process, rather than spawning child processes.
3. Unifies various types that were duplicated across each Runner for
more consistency and easier boilerplating of new Runners.
## Description
This makes progress toward #15917 by deleting test-gc-sweep-tests, which
is not needed anymore as per @agarwal-navin.
PACKAGES.md was updated using `flub check layers --info
./build-tools/packages/build-tools/data/layerInfo.json --md .`.
1. Eliminates the "hosts" directory.
2. Declares "data-objects" to be specifically for webpack-fluid-loader
examples (examples not using webpack-fluid-loader either move to "apps"
or a more specific location). Added a README to indicate this.
3. Sets up several subdirectories for more-specific and meaningful topic
groupings:
* benchmarks
* external-data
* version-migration
* view-integration
4. Moves examples under /experimental into the /examples directory in
their appropriate location. /experimental/examples is eliminated.
5. Rescopes `@fluid-experimental/inventory-app` to
`@fluid-example/inventory-app`
6. Moves `@fluid-experimental/tree-react-api` to /experimental/framework
7. Fixes up some incorrect `repository.directory` entries in
package.jsons
## Description
Renames the `@fluid-internal/tree` package to
`@fluid-experimental/tree2`. This will make it included in releases
while clearly marking it as experimental. This change is simply being
done so contributors to the tree package can have packages builds to
test with.
Currently all public releases (internal, LTS, prerelease and test)
include the same set of packages, which includes `@fluid-experimental`
but not `@fluid-internal/tree`, so this change results in the package
being included in these builds.
All APIs in `@fluid-experimental/tree2` are marked as `@alpha`. This is
redundant with them being in an experimental package: both mean no API
stability commitment is being made and no data format compatibility
commitment is being made.
`pnpm run layer-check --md` was run to update PACAKGES.md. Looks like it
was out of date so some other updates are included.
## Breaking Changes
Uses of the previously non-public `@fluid-internal/tree` package will
need to update to `@fluid-experimental/tree2`
## Moving test-end-to-end-tests to fluid-internal scope
We are trying to reduce our API surface, and we thought starting with
some of the testing tools found under packages/test would cause the
least friction.
test-end-to-end-tests is not used within LoopSDK, office-bohemia or
whiteboard-app
[AB#3720](https://dev.azure.com/fluidframework/235294da-091d-4c29-84fc-cdfc3d90890b/_workitems/edit/3720)
---------
Co-authored-by: Tyler Butler <tyler@tylerbutler.com>
## Description
After some discussion on namespacing conventions, we're moving
`@fluidframework/attributor` back to the `@fluid-experimental` namespace
until we're ready to remove the @alpha tag from its APIs. This more
accurately reflects its status as ready for usage in dev branches and
welcoming feedback on API surface.
Similar to #14086 and #14127. Unprivate because test-end-to-end-tests
depends on it to be installable from internal artifact feeds.
Also realized I had put the breaking change notice in the wrong section,
so moved it to the right one.
Providing a code loader implementation is not core to the value
proposition of Fluid, and is a particularly dangerous piece of code to
prescribe given its responsibility of fetching and running arbitrary
code. This change would deprecate our implementation offering and
associated interfaces.
Hosts-sample example uses web-code-loader, but also is not really needed
anymore (I would point customers at the schema-upgrade demo for code
migration instead). I remove that example here. We should probably
consider rearranging the directory structure of our examples, but I
don't do that in this change.
Examples should use the example scope, and we should avoid publishing
them to NPM. This change moves the PropertyDDS examples to that scope
accordingly and marks them private.
Same idea as #14086, this prevents test-version-utils from publishing.
Verified:
* Not a dependency of merge-tree, sequence, or fluid-experimental/tree
(which would break the fuzz tests)
* Not a dependency of map, matrix, or fluid-internal/tree (which would
break the perf tests)
Also, a bad merge changed the build tool packages back to a prerelease
version which was causing a build break. This change also moves them
back to the released ^0.9.0 version.
I believe both of these packages are intended to only be used as
internal tools for our testing, and not for public consumption. This
change moves them to the `@fluid-internal` scope and marks them as
`"private": true` which means they will no longer be published either on
internal feeds or public ones. It also stops generating typetests and
documentation (as these are internal packages with no public API to
document and no type compat guarantees version-to-version).
There are several other packages that could get the same treatment, but
I wanted to start with just a couple to make sure this is on the right
track.
If approved/merged, then I'll add a note in `main` branch's
`BREAKING.md` in a followup.
## Description
Renames @fluid-internal/attributor to @fluidframework/attributor and
makes the package public. All APIs are still marked alpha, but it's in a
good enough state to start getting feedback from partner teams.
Craig Macomber (Microsoft)
Jason Hartman
Matt Rakow
Noah Encke
Sonali Deshpande
Daniel Lehenbauer
Tong Chen
Joshua Smithrud
Tyler Butler
Ji Kim
Zach Newton
Abram Sanderson
Rishhi Balakrishnan
Abram Sanderson
Sonali Deshpande
Scott Norton