## Description
Adds a new package `@fluid-experimental/ai-collab` with the first draft
of a library that simplifies integration with AI / LLM agents in
Fluid-based applications.
Also adds a sample application that leverages said package. NOTE: we
know already that the app will probably be re-written so we're not
spending more time fixing its source code.
---------
Co-authored-by: seanimam <105244057+seanimam@users.noreply.github.com>
Co-authored-by: Tyler Butler <tyler@tylerbutler.com>
## 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 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.
Two reasons for removal:
1. It's no longer used. As the tree API simplified, it was easier for
samples to include the few lines of idiomatic React code than import
this package.
2. It imports non-public APIs in order to support older tree API
variants.
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`.
## Description
This PR moves the ID compressor into a separate package, cleaning up the
dependency structure and making it possible to depend on it in places
where depending on the runtime is disallowed or inappropriate.
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
Uses the --outFile argument instead of console redirect so the output
files doesn't get overwritten if there is an error.
---------
Co-authored-by: Tyler Butler <tyler@tylerbutler.com>
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
As we add/remove/move packages, these lists will change and we can use
them to verify _before we run the publishing pipeline_ what will be
published. The CI pipeline just publishes the packages in each list to
the feed in question. This makes it far less likely that we find out a
package is missing in a feed only after we do a release.
They are generated by running the `generate:packageList` script from the
root of the release group. They are also generated during a build, so
these files are kept up-to-date as changes are made.