-
Notifications
You must be signed in to change notification settings - Fork 338
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: always reject invalid requests #1101
Conversation
e50fdee
to
727ae06
Compare
727ae06
to
fa0453a
Compare
ee70058
to
e2ebccb
Compare
6094a55
to
2154727
Compare
2154727
to
6a5cd97
Compare
6a5cd97
to
f36cce0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job, as far as I understanding for now. I added few comments and questions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job 👍
@@ -10,6 +10,8 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), | |||
|
|||
## Fixed | |||
|
|||
- Prism will now correctly refuse invalid requests even when used with the `proxy` command [#1101](https://github.com/stoplightio/prism/pull/1101) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so long as --errors
is enabled?
This PR has a good thing and a bad thing.
The good: closes #1091, makes a better use of typings here and there and it also removes a deprecation warning
The bad: it closes the bug in a way that's not cool (basically duplicating some efforts here and there) and shows that it is probably time to resume the rethinking of the validation process that started some time ago. You can find more details on #1135