Filter with authData "key does not exist" shows incorrect results

[mtrezza]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.

Issue Description

When setting a data browser filter on field authData, condition key does not exist, value facebook, it shows records that contain auth data with key facebook, but with the authData field empty. That means, not only does it show the records even though it should not show them, the record itself is incorrect as it has an empty authData field which is not the case.

Steps to reproduce

Given the following records in _User:

• objectId: a, authData: (empty)
• objectId: b, authData: { 'facebook': ...}

Filter condition key does not exist, value facebook shows:

• objectId: a, authData: (empty)
• objectId: b, authData: (empty)

but it should show:

• objectId: a, authData: (empty)

Environment

Dashboard

• Parse Dashboard version: 6.0.0-alpha.11

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mihir2004]

Is this issue still open?

[mtrezza]

@mihir2004 it is up for grabs, would you be interested?

[mihir2004]

@mtrezza I would like to give it a try could you please assign this to me

[mtrezza]

You just assigned it to yourself :-) There is no official assignment process. As long as there is an ongoing PR with reasonably frequent updates, it should be clear to others that this is being worked on. See also the Parse Bounty Program.