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

Remove invalid output tests #670

Merged
merged 1 commit into from
Oct 23, 2023

Conversation

marksparkza
Copy link
Contributor

The 2019-09 and 2020-12 specifications do not require an output unit to be generated for a passing keyword that does not produce an annotation.

The 2019-09 and 2020-12 specifications do not require an output unit to be generated for a passing keyword that does not produce an annotation.
@marksparkza marksparkza requested a review from a team as a code owner April 22, 2023 20:25
@gregsdennis
Copy link
Member

Thanks for this. I'll have a deeper look tomorrow.

For now, I wonder if this is moot. We might be revamping these tests anyway. #657 I would consider these tests as WIP for now (I should update the readme.)

@Julian
Copy link
Member

Julian commented Oct 20, 2023

@gregsdennis what's the conclusion on this one? We should probably axe these if they're wrong (which I haven't looked myself), even if we're still redoing the test format.

Copy link
Member

@gregsdennis gregsdennis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think removing these are fine. Basic and detailed were supposed to eliminate superfluous nodes. Verbose shows everything.

I'm of the opinion that the entire output testing thing needs to be rethought.

@gregsdennis gregsdennis merged commit 451baca into json-schema-org:main Oct 23, 2023
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

Successfully merging this pull request may close these issues.

3 participants