Repository navigation
v0.5.0
Added
-
morg --help,morg -hand a baremorgprint usage: the
normalizecommand, every flag with its argument and a one-line
description, and a few worked examples.morg --versionprints the
installed version. A bare invocation previously failed on formats it
could not determine, which told a first-time reader nothing about
what the CLI accepts; there was no way to ask at all.The help text is rendered from the same table the parser dispatches
on, so it cannot document a flag that does not exist or omit one that
does.
Changed
-
The site names the npm package and links it. The landing page says
morg is also a CLI and a library, published as@remigius42/morg,
and shows thenpxline that runs it without an install; both pages
carry an npm link in the nav beside GitHub. Until now the only route
from the Web UI to the package was the repository, which documents it
but does not hand it over.The nav had fit 320px exactly, so a fourth item would have put the
whole page into a horizontal scroll: the nav lists now wrap, which
costs a second row on the narrowest phones and leaves every wider
viewport as it was.
Fixed
- An unsupported format names the value it rejected, as in
Unsupported format 'notes.md', rather than only the two it
accepts, and a value that has a file extension is answered with the
likely correction:--fromand--totake a format name, and the
file belongs to--inputor--output. They sit beside each other
and read alike, so a file name in the wrong one is an easy mistake that
the old message left the reader to find unaided. Failures that come
from the invocation now also point atmorg --help.