Set the 'type' param so that future calls will know its type#99
Merged
dmdhrumilmistry merged 1 commit intoOWASP:devfrom May 12, 2024
Merged
Set the 'type' param so that future calls will know its type#99dmdhrumilmistry merged 1 commit intoOWASP:devfrom
dmdhrumilmistry merged 1 commit intoOWASP:devfrom
Conversation
Contributor
Author
|
Can you please merge this? it is making |
Contributor
Author
dmdhrumilmistry
approved these changes
May 12, 2024
Collaborator
Hi @nrathaus, apologies for the delayed response. I was bit occupied this week. I've tested it manually and changes made in this PR seems to be working fine. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scanning the end point of https://brokencrystals.com/swagger-json disclosed some false negatives caused by not setting the
typefield, makingpayloadvalues to not get set to their new value