Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cli output for daisy202-validator should not only writing to a html file #584

Open
tigexplorer opened this issue Feb 16, 2021 · 5 comments

Comments

@tigexplorer
Copy link

Please fill out the outline following the instructions below. Remember, this is for reporting bugs and issues and not a place to ask questions. For that, you can contact us via our developers mailing list

Expected Behavior

Instead of writing the output in a html file, I wish to have it as direct output in the terminal

Actual Behavior

/opt/daisy-pipeline2-cli/dp2 daisy202-validator --ncc /home/user/test/ncc.html --output test

writes the output in the subdir of test in test/html-report/html-report.html

Steps to Reproduce

Provide a list of steps taken to reproduce the problem.

Details

Is there an option for direct output?

Environment

  • Operating system: ubuntu 20.4
  • DAISY Pipeline 2 version: 1.12.1
  • Interface: Command Line

Logs

Visit Providing Logs in an Issue for details on how to provide your log files.

[Logs]( link goes here )

@bertfrees
Copy link
Member

Are you expecting the full validation report in plain textual format, or merely a valid/invalid state?

@tigexplorer
Copy link
Author

Are you expecting the full validation report in plain textual format, or merely a valid/invalid state?

A valid state or al list with invalid items.

@tigexplorer tigexplorer changed the title cli output for daisy202-validator should not writing to a html file cli output for daisy202-validator should not only writing to a html file Feb 16, 2021
@bertfrees
Copy link
Member

OK. And the purpose being what exactly?

@tigexplorer
Copy link
Author

For viewing the result, no additional step is necessary (going to the html site).
Also, the result maybe can be used to "pipe" directly in other scripts or software.

@bertfrees
Copy link
Member

I have considered such a feature but I think the use case isn't strong enough.

If for any reason you need a text version of the report, you may render the HTML report using a tool like w3m or elinks.

Examples:

w3m -dump report.html
elinks -dump report.html

Regarding integration of our CLI into scripts, I think there are some features that would be convenient:

Let me know if these would help you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants