We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Consider I have the next specification toward my response body:
{ "username": "admin", "notExistingProp": true }
When the actual response body is:
{ "username": "admin", "extraPropA": "...", "extraPropB": "..." }
I see both extraPropA and extraPropB as new added properties, but I don't see the notExistingProp as red missing property.
extraPropA
extraPropB
notExistingProp
Perhaps a logic flaw during the analyzis if a property is missing:
gavel2html/src/converter.coffee
Lines 137 to 144 in 99897d7
The text was updated successfully, but these errors were encountered:
Still actual and is the reason for this behavior present in the core app.
Sorry, something went wrong.
No branches or pull requests
What
Consider I have the next specification toward my response body:
When the actual response body is:
I see both
extraPropA
andextraPropB
as new added properties, but I don't see thenotExistingProp
as red missing property.Why
Perhaps a logic flaw during the analyzis if a property is missing:
gavel2html/src/converter.coffee
Lines 137 to 144 in 99897d7
The text was updated successfully, but these errors were encountered: