Joshua Smithrud

This commit introduces a **new feature** to the **`eslint-config-fluid`** configuration by enabling the `@eslint-community/eslint-comments/require-description` rule. This rule semantically enforces that all `eslint-disable` comments must be accompanied by a description explaining their purpose, automating a crucial code quality guideline previously handled during manual PR reviews. Configured as a **warning**, this change aims to improve code maintainability and clarity without being immediately disruptive. It provides developers with automated feedback on their ESLint disable justifications, enhancing the overall consistency and understanding of code exceptions.

feat(text-editor): Add devtools initialization to app setup (#26581)

This commit introduces a **feature enhancement** to the **`eslint-plugin-fluid`** package, specifically updating the `no-file-path-links-in-jsdoc` rule. The rule now **permits the inclusion of file path links within `@privateRemarks` blocks** in JSDoc comments, as these links do not impact published API documentation or end-user experience. This change provides developers with more flexibility for internal documentation without affecting public-facing content. Additionally, it includes a **refactoring** effort to extract common **TSDoc-parsing utilities**, improving code reusability across various TSDoc-related ESLint rules within the plugin.

This commit **promotes the `TableSchema` APIs from alpha to beta**, signifying increased stability and readiness for broader use within the **`tree` DDS** and the **`fluid-framework`** package. This **API stabilization** involves updating API reports for both packages to officially expose the `System_TableSchema` and `TableSchema` namespaces. Additionally, the internal schema naming convention for tables has been updated from `table` to `tableV2` to reflect this evolution, impacting relevant source files like `tableSchema.ts` and test snapshots. This change makes the `TableSchema` APIs more robust and officially available for broader consumption by developers.

This commit introduces a **new capability** to the **SharedTree DDS** by adding the `minVersionForCollab` option to `configuredSharedTreeBeta`. This option, exposed via `CodecWriteOptionsBeta` within `SharedTreeOptionsBeta`, allows developers to specify a minimum version required for collaborative operations, enhancing compatibility control. Concurrently, the `MinimumVersionForCollab` type alias is **promoted to beta** within `runtime-definitions`, removing its `@legacy` tag. This work is a **prerequisite for promoting `TableSchema` APIs to beta**, signifying a step towards broader API stabilization and future public API use.

This commit performs **documentation cleanup** by **clarifying existing descriptions** within the project's changesets, ensuring more precise release notes. It specifically improves the explanation of the `'push'` alias for the `insertAtEnd` method on `TreeArrayNode`, enhancing understanding of this **data structure operation**. Additionally, the commit clarifies the optional `'label'` parameter for the `runTransaction` function, providing better context for **transaction management**. This **maintenance** work directly impacts the **clarity of documentation** for these specific features, benefiting developers and users.

This commit performs a significant **refactoring** and **maintenance** upgrade within the **`driver-utils`** package. The ESLint configuration for `packages/loader/driver-utils` has been promoted from `minimalDeprecated` to the stricter `recommended` preset, necessitating widespread code adjustments to resolve new violations. These changes primarily involve updating import/export statements to use `import type` and `export type` for improved type-only imports, enhancing type safety through better annotations and assertions, and refining error handling logic across various core utilities. This effort, which also adds a missing `@types/lz4js` dev dependency, improves code quality and maintainability for critical driver functionalities like compression, networking, and storage.

refactor(examples/benchmarks): Promote eslint config from "minimalDeprecated" to "recommended" and fix violations (#26313)

This commit significantly **improves API documentation** across numerous **Fluid Framework packages**, including DDSes, drivers, loader utilities, and various test and tooling modules. It primarily involves **adding missing JSDoc descriptions** to functions, methods, and types, which enhances IntelliSense and the quality of published API documentation. This **documentation improvement** is a crucial **maintenance** step towards enabling stricter ESLint enforcement of JSDoc rules, ensuring comprehensive and consistent code descriptions. Additionally, it cleans up API reports by removing `(undocumented)` tags and strategically disables JSDoc enforcement for deprecated `sequence-deprecated` components. This work is part of an ongoing effort to streamline ESLint configurations and elevate overall API clarity.

refactor(examples/apps): Promote eslint configs from "minimalDeprecated" to "recommended" and fix violations (#26290)

feat(eslint-config-fluid): Enable "recommended" rules in "minimal-deprecated" as warnings (#26190)

This commit **promotes the `jsdoc/multiline-blocks` ESLint rule** from the `recommended` to the `minimal` configuration within the **`eslint-config-fluid`** package. This **configuration enhancement** enforces a consistent multi-line block style for all JSDoc comments, improving code readability and maintainability. As a direct consequence, various JSDoc comments across **PropertyDDS** and **DDS Tree** packages, such as in `changesetConflictTypes.ts` and `valueArrayProperty.js`, were **updated to fix resulting linter violations**. This work is a **maintenance fix** and a step in a larger **refactoring effort** to consolidate ESLint configurations by collapsing `recommended` and `minimal-deprecated` configs.

This commit **refactors** the project's ESLint configuration by **promoting the `no-empty` rule** from the "recommended" set to the "minimal" set, aligning with an ongoing effort to consolidate configurations. To comply with this stricter rule, **numerous violations were fixed** across various packages, including `driver-base`, `loader/driver-utils`, and several `test` and `tools` modules. The fixes primarily involve **adding `TODO` comments to empty catch blocks** or `eslint-disable` directives to ensure all empty blocks are explicitly acknowledged. This **maintenance** work improves code quality and consistency across **core driver components, testing infrastructure, and developer utilities**.

This commit **promotes the `@typescript-eslint/no-import-type-side-effects` ESLint rule** from "recommended" to "minimal" within the **`eslint-config-fluid`** package. This **refactoring** effort enforces the use of `import type` for all type-only imports, improving **code quality** and potentially **build efficiency** by preventing accidental runtime side effects. As a result, numerous files across **core Fluid Framework DDSs** (e.g., `experimental/dds/tree`, `packages/dds/sequence`), **driver components**, and a **wide array of test files** were updated to comply with the stricter linting. This change is part of an ongoing **maintenance** initiative to streamline ESLint configurations.

This commit performs **ESLint configuration cleanup** by removing redundant rule overrides from numerous package-level configuration files across the **`packages/dds`**, **`packages/drivers`**, **`packages/framework`**, and **`packages/utils`** directories. Specifically, it targets rules like `consistent-type-exports`, `consistent-type-imports`, and `no-import-type-side-effects` that were previously overridden locally but are now consistently handled by the base ESLint configuration. This **maintenance** task streamlines the project's linting setup, reducing configuration overhead and improving consistency without altering any runtime behavior or functional aspects of the code. The change primarily impacts the **development environment** and **build process**, ensuring a cleaner and more efficient linting pipeline.

refactor(example-utils): Promote eslint config from "minimal-deprecated" to "recommended" and fix violations (#26159)

This commit **updates the ESLint configuration** within the `eslint-config-fluid` package, specifically modifying the `jsdoc/multiline-blocks` rule. It is a **feature enhancement** that now **permits single-line JSDoc/TSDoc comment syntax** for single-line comments, relaxing the previous requirement for all JSDoc/TSDoc comments to use multi-line syntax. This change aligns the linting rules with a prior team decision, providing developers with more flexible and concise comment formatting options. The **ESLint configuration** for JSDoc/TSDoc comments is directly affected, impacting how developers write and lint documentation comments across the project.

This commit **promotes** the `@typescript-eslint/explicit-function-return-type` ESLint rule from a recommended setting to a stricter, minimal requirement across the repository. This **configuration update** aims to improve code quality and maintainability by enforcing explicit return types for functions. While most of the codebase already adheres to this rule, the **ESLint configuration** for `experimental/dds/tree` temporarily disables it, and `packages/dds/sequence` and `packages/test/test-end-to-end-tests` set it to a warning. This **code quality improvement** ensures more consistent and readable type annotations, with temporary exceptions noted for future resolution.

This commit **improves the `eslint-config-fluid` configuration** by **disabling the `unicorn/no-array-callback-reference` rule**. This specific ESLint rule was generating **false positives** when non-array methods happened to share names with standard array methods, leading to unnecessary `eslint-disable` directives throughout the codebase. This **configuration improvement** primarily affects the **ESLint setup** across the project, allowing for the removal of previous workarounds in modules such as **`@fluidframework/map`**, **`@fluidframework/odsp-driver`**, and **`@fluidframework/tree-agent`**. The change streamlines code style enforcement, **reduces noise** in the linter output, and enhances overall code readability by eliminating redundant suppression comments.

This commit introduces **explicit return types** to numerous functions, methods, and getters across the **`test-end-to-end-tests`** and **`test-service-load`** packages. This extensive **refactoring** effort enhances type safety and code clarity within the test suite, also incorporating `type` imports where appropriate. The changes are purely for **code quality and maintainability**, with no functional impact on the tests themselves. This work is a foundational step towards enabling global ESLint enforcement, improving overall code robustness and adherence to coding standards.