FluidFramework/feeds
Craig Macomber (Microsoft) 8db660e2d4
Remove PropertyDDS packages which are not depended on by PropertyDDS (#22326)
## 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
2024-09-05 16:14:28 +00:00
..
README.md
internal-build.txt
internal-dev.txt
internal-test.txt
public.txt

README.md

The files in this folder are lists of packages that should be published to the four npm feeds that we publish to. They provide an "audit" of what should go where.

As we add/remove/move packages, these lists will change and we 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.