Draft: Resolve "API fuzz show alternative message when "body" is not available"
What does this MR do?
Follow-up to: !50731 (merged)
Bug fix:
"" or empty string is considered falsely, but we want don't want to show the empty body message if it's an empty string. Even though it's a blank string, it's not explicitly an empty body from the server. We only consider "null" or "undefined" to show the empty body message.
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #284677 (closed)