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

fix(output): don't allow empty outputs #24

Merged
merged 1 commit into from
Mar 31, 2024
Merged

Conversation

khaosdoctor
Copy link
Member

Outputs will always have at least one response, requests cannot respond to nothing so now outputs do
not allow empty responses

BREAKING CHANGE: Any empty outputs will now fail type check. Any endpoints MUST now have at least
one key in the output object

Outputs will always have at least one response, requests cannot respond to nothing so now outputs do
not allow empty responses

BREAKING CHANGE: Any empty outputs will now fail type check. Any endpoints MUST now have at least
one key in the output object
@khaosdoctor khaosdoctor merged commit 25dc301 into main Mar 31, 2024
3 checks passed
@khaosdoctor khaosdoctor deleted the fix/required-output branch March 31, 2024 00:04
Copy link

🎉 This PR is included in version 7.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

1 participant