Closed eightfilms closed 2 years ago
Thinking on this more, perhaps it is better to use two distinct commands for documenting commands and plugins separately?
E.g. command reference goes under the commands chapter, and then we can add a similar reference for the plugins we ship (i.e. forc-fmt
, forc-lsp
) under the plugins chapter.
Keeping in mind the mdbook publishing CI would need to be updated to first install each of the plugins so that they're available to the forc plugins
command.
Yup, definitely makes sense regarding the documentation. In that case perhaps a more appropriate name for this issue is mdbook-forc-documenter: support documentation for native plugins
Related discussions about
forc --list
: https://github.com/FuelLabs/sway/pull/1047#discussion_r846969076 https://github.com/FuelLabs/sway/issues/702Currently,
forc-documenter
usesforc --help
to generate documentation for forc commands. When/if we haveforc --list
ready to support listing forc commands + forc plugins, we should use that instead.