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

Expected YAML output for multiple messages #30

Open
torarnv opened this issue Mar 17, 2022 · 2 comments
Open

Expected YAML output for multiple messages #30

torarnv opened this issue Mar 17, 2022 · 2 comments

Comments

@torarnv
Copy link

torarnv commented Mar 17, 2022

The current spec describes a case for reporting messages via the YAML format:

TAP version 13
1..N
ok 1 Description # Directive
# Diagnostic
  ---
  message: 'Failure message'
  severity: fail
  data:
    got:
      - 1
      - 3
      - 2
    expect:
      - 1
      - 2
      - 3
  ...
ok 47 Description
ok 48 Description

What is the expected output when multiple messages are emitted?

  ---
    -
      message: 'Debug message'
      severity: debug
    -
      message: 'Warning message'
      severity: warning
  ...

This seems to be somewhat supported by the old archived spec, but breaks the assumption that the root namespace is a hash?

Do any producers or consumers today support this use-case in any way?

@torarnv
Copy link
Author

torarnv commented Mar 17, 2022

See also #9

@isaacs
Copy link
Contributor

isaacs commented Apr 19, 2022

The details of the yaml diagnostic block is still currently unspecified. (Apart from "it's YAML!")

It would be good to do a survey of implementations and see what overlap there is. If we have quorum, that'd be a good thing to provide some guidance on.

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