Skip to content
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

docs: Update package READMEs to leverage markdown-magic header and footer templates #22013

Merged
merged 6 commits into from
Jul 24, 2024

Conversation

Josmithr
Copy link
Contributor

Also makes a few misc. cleanup changes

@Josmithr Josmithr requested a review from a team July 24, 2024 21:10
@github-actions github-actions bot added base: main PRs targeted against main branch area: dds Issues related to distributed data structures area: dds: tree area: dev experience Improving the experience of devs building on top of fluid area: driver Driver related issues area: examples Changes that focus on our examples area: loader Loader related issues area: tests Tests to add, test infrastructure improvements, etc labels Jul 24, 2024
@@ -1,5 +1,14 @@
# @fluid-example/table-document

<!-- AUTO-GENERATED-CONTENT:START (LIBRARY_README_HEADER) -->
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: this is a case that was not previously considered. We do a have a few example libraries in addition to example apps. We will want to update the library README header template to include a notice for example libraries. Ideally, these shouldn't be published. But this package, in particular, is (see the note starting on line 30 for context). Anyone who sees this package on npm or in our github should be confronted with a notice about the nature of this libarary.

Will address in a follow-up PR. Leaving the template here for now so it will auto-update with that PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -28,7 +57,6 @@ The order of the edits is:
1. All acknowledged edits, in the order agreed upon by Fluid's consensus.
2. All local edits (not acknowledged by Fluid yet), in the order they were applied.

**Important: this DDS is no longer in active development, and a non-experimental, officially supported SharedTree is in active development by the Fluid team that will expand on its rich feature set.**
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note for reviewers: Moved this to the top of the README and updated it to point to the new tree library.

**Topics covered below:**

- [@fluidframework/container-loader](#fluidframeworkcontainer-loader)
- [Using Fluid Framework libraries](#using-fluid-framework-libraries)
- [Installation](#installation)
- [Importing from this package](#importing-from-this-package)
- [API Documentation](#api-documentation)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These contents were out of date.

@@ -1 +1,46 @@
# @fluid-internal/functional-tests

TODO: Document this package
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not for this PR, but we shouldn't have packages (even private ones) without basic documentation explaining what they are.

@@ -4,18 +4,6 @@ _Note: This tool has dependencies on Microsoft-internal systems._

NodeJs-based test to simulate many clients and a high rate of op generation.

<!-- AUTO-GENERATED-CONTENT:START (LIBRARY_README_HEADER) -->
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note for reviewers: this package isn't a library, it just contains tests. So the library header really isn't appropriate.

@msfluid-bot
Copy link
Collaborator

@fluid-example/bundle-size-tests: +245 Bytes
Metric NameBaseline SizeCompare SizeSize Diff
aqueduct.js 457.99 KB 458.02 KB +35 Bytes
azureClient.js 555.23 KB 555.28 KB +49 Bytes
connectionState.js 680 Bytes 680 Bytes No change
containerRuntime.js 258.67 KB 258.68 KB +14 Bytes
fluidFramework.js 405.21 KB 405.22 KB +14 Bytes
loader.js 134.04 KB 134.05 KB +14 Bytes
map.js 42.13 KB 42.14 KB +7 Bytes
matrix.js 146.41 KB 146.42 KB +7 Bytes
odspClient.js 523.37 KB 523.42 KB +49 Bytes
odspDriver.js 97.55 KB 97.57 KB +21 Bytes
odspPrefetchSnapshot.js 42.61 KB 42.62 KB +14 Bytes
sharedString.js 163.13 KB 163.14 KB +7 Bytes
sharedTree.js 395.72 KB 395.73 KB +7 Bytes
Total Size 3.3 MB 3.3 MB +245 Bytes

Baseline commit: 90ddf1c

Generated by 🚫 dangerJS against 5f6b687

@@ -26,7 +26,7 @@ function initializeTinyliciousClient(): TinyliciousClient {
}
```

<!-- AUTO-GENERATED-CONTENT:START (EXAMPLE_GETTING_STARTED:usesTinylicious=FALSE) -->
<!-- AUTO-GENERATED-CONTENT:START (EXAMPLE_README_HEADER:usesTinylicious=FALSE) -->

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do the contribution guidelines need to be added here too?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They're already included toward the bottom of the file

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A handful of these already contained the footer pragma, but were using only a subset of the header contents.

@Josmithr Josmithr merged commit 52dc0d3 into microsoft:main Jul 24, 2024
30 checks passed
@Josmithr Josmithr deleted the update-readmes branch July 24, 2024 22:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: dds: tree area: dds Issues related to distributed data structures area: dev experience Improving the experience of devs building on top of fluid area: driver Driver related issues area: examples Changes that focus on our examples area: loader Loader related issues area: tests Tests to add, test infrastructure improvements, etc base: main PRs targeted against main branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants