parse-community / parse-community/parse-dashboard

API REST Console Query Parameters with "keys" doesn't work as expected

Open
#2,521 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:bug
Dominant language
JavaScript
Stars
3.8k
Forks
1.4k
PR merge metrics
No merged PRs in 30d

Description

New Issue Checklist
Issue Description

using keys={"key"} in query parameters in API Console doesn't return results with the key(s) only as expected but returns nothing but the objectId, createdAt, updatedAt keys which I did not want. even objectId, createdAt, updatedAt should not be given.

Steps to reproduce

use keys={"key"} on a class in the REST API Console

Actual Outcome
{
    "results": [
        {
            "objectId": "Ciptig0mA9Nwpd6ri9uF4t81rTUOO2YE",
            "createdAt": "2024-01-18T17:40:05.894Z",
            "updatedAt": "2024-01-18T17:40:05.894Z"
        }
    ]
}
Expected Outcome
{
    "results": [
        {
            "key": "value"
        }
    ]
}

Environment

Dashboard

  • Parse Dashboard version: 5.3
  • Browser (Safari, Chrome, Firefox, Edge, etc.): Safari
  • Browser version: 17.1

Server

  • Parse Server version: 6.3
  • Operating system: Mac OS 14.1.1
  • Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): local

Database

  • System (MongoDB or Postgres): Postgres
  • Database version: 15.2
  • Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Local
Logs

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the API REST Console and reproduce the query using keys={"key"} against a class. Trace how the query parameter is handled and verify that the response contains the requested key field rather than only objectId, createdAt, and updatedAt.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.