Adalennis opened a new issue, #9269:
URL: https://github.com/apache/hop/issues/9269

   ### What needs to happen?
   
   `hop help` lists 13 commands, but the Hop Tools section doesn't cover all of 
them, and its navigation and index page list different pages.
   
   **Missing commands**
   
   - `hop export` (added in #8349) exports pipeline, workflow and model 
diagrams to SVG, Mermaid and other formats, for one file (`-f`, `-o`) or a 
folder (`-s`, `-t`, `-r`), with `--format`, `-m/--magnification`, 
`-in/--include-notes` and `--list-exporters`. The assembly also ships 
`hop-export.sh` / `hop-export.bat`. The command is only mentioned in the dev 
manual's diagram exporters page.
   - `hop driver list` / `hop driver install` are described in a paragraph on 
`database/databases.adoc`, but have no Hop Tools page. The `install` options 
`--force`, `--target` and `--repo` are not documented anywhere.
   - The `hop help` sample on `hop-tools/hop.adoc` shows 9 commands: `driver`, 
`export`, `marketplace` and `naming-check` are missing.
   
   **Navigation and index**
   
   - The navigation has `hop lint`, the index page doesn't.
   - The index page has Hop (`hop.adoc`), Hop Python and Hop Arrow, the 
navigation doesn't.
   - `hop doc` has two pages. The navigation links `hop-doc/index.adoc`, which 
doesn't document `-gh/--generate-html` and `-rmmd/--remove-markdown`. The index 
page and "The Hop toolbox" link `hop-tools/hop-doc.adoc`, added with those 
options in #6295.
   
   Add pages for `hop export` and `hop driver`, refresh the `hop help` sample, 
make the navigation and the index list the same pages, and merge the two `hop 
doc` pages into one.
   
   ### Issue Priority
   
   Priority: 3
   
   ### Issue Component
   
   Component: Documentation


-- 
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]

Reply via email to