Closed ahansen90 closed 5 years ago
Yeah, the design here needs reconsidering (perhaps at the compiler level too). pulp docs
assumes that any documentation generated by purs docs
is written to a file, so it ignores any data which appears on stdout. As you probably realised, you’ll just need to call purs docs
directly for now.
@asturtz2 do you think it would be sensible if purs docs --format [ctags|etags]
wrote to a file [TAGS|tags]
by default instead of writing to stdout?
Closing this as we're going to address it in the compiler.
When I try
pulp docs -- --format ctags
, I get the following output:However, nothing is generated, not in
generated-docs
or anywhere else. If I just runpulp docs
, it works correctly (generating markdown files ingenerated-docs
).Commands used to test:
mkdir ctags-test && cd ctags-test
pulp init
bower install
pulp docs -- --format ctags
With this same test project, I can do
purs docs --format ctags bower_components/**/*.purs src/**/*.purs
and it will correctly output the ctags to standard output, so I don't think this is an issue withpurs
.pulp
version: 12.3.1,purs
version: 0.12.2