MR widget stops adding code quality degradations after one invalid object
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
The MR code quality widget stops adding code quality degradations after one invalid object.
Steps to reproduce
Create a code quality report from this JSON:
[{"fingerprint":"d5d779c2f916d3a6075f705729470da0","description":"Issue number 1","location":{"lines":{"end":1,"begin":1},"path":"test.py"},"severity":"major"},{"fingerprint":"f3689c6459561caf07066081e3b96a67","description":"Issue number 2","location":{"lines":{"end":3,"begin":3},"path":"test.py"}},{"fingerprint":"eccbc87e4b5ce2fe28308fd9f2a7baf3","description":"Issue number 3","location":{"lines":{"end":6,"begin":6},"path":"test.py"},"severity":"major"}]
The second object is missing the "severity" key and value, and will be missing from the MR widget. Even though it shows up in the pipeline info under the Code Quality tab.
Example Project
What is the current bug behavior?
The MR widget only shows up until the first invalid code quality object.
What is the expected correct behavior?
The MR widget should show all valid code quality objects.
Relevant logs and/or screenshots
n/a
Output of checks
This bug happens on GitLab.com
Possible fixes
Not sure
Edited by 🤖 GitLab Bot 🤖