xuang7 opened a new pull request, #9032: URL: https://github.com/apache/texera/pull/9032
### What changes were proposed in this PR? This PR adds a generator that builds the operator reference pages under `docs/reference/operators/` from the annotations on each operator class, so the pages can be regenerated from the source code instead of edited by hand. Changes: - A new `OperatorReferenceGenerator` sbt module at `docs/operator-reference/`, depending only on `WorkflowOperator`. - `JsonPropertyReflectionUtils` reads an operator class and renders its property table (title, requirement, type, default, description, with nested config classes and switch-dependent properties indented under their parent), the UDF code template, the output ports, and the sklearn hyperparameter enums. - `OperatorDocScanner` writes one page per operator in its group directory, an index per group, the root index, and the parameter pages. It regenerates everything under the output directory except the hand-written `output-modes.md`. Run it from the repository root with `sbt "OperatorReferenceGenerator/runMain org.apache.texera.operatorreference.OperatorDocScanner"`. - The module runs its tests in the amber CI job and is excluded from the docs-to-website sync, since it is build tooling rather than docs content. No page is changed in this PR. The regenerated pages follow in a separate PR so their diff can be reviewed on its own. ### Any related issues, documentation, discussions? Closes #9031 ### How was this PR tested? `sbt OperatorReferenceGenerator/test` (14 tests), `scalafmtCheck` and `scalafix --check` pass. Running the generator on current main produces the pages submitted in the follow-up PR. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Fable 5.1) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
