parse-community / parse-community/parse-dashboard
Keep cell selected after data browser refresh
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
When clicking "Refresh" in the data browser, the cell stays selected in the same row / column position, even if the document moved to a different row. The user may mistake the selected cell as being the previously selected cell which can lead to user errors.
Feature / Enhancement Description
- Remember the
objectIdand selected field of the document and select the same cell even if its position has moved. Also the field name should be explicitly remembered, instead of just the row / column coordinates. - If the specific document and field are not in the data browser anymore after a refresh, no cell should be selected to avoid confusion.
Example Use Case
- Browse to
_Userclass. - Sort ordered by
createdAt. - Select a cell in row 1 (document A).
- Refresh the data browser.
- Assuming that a new document B has been created in the meantime, that is now in row 1.
- The selected cell is now of document B instead of document A, but it should be in row 2 of document A.
Alternatives / Workarounds
None.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the data browser's Refresh action and the code that tracks the selected cell. Trace how the selected document and field are represented across a refresh, then verify the example with a sorted _User class: the same objectId and field remain selected, or no cell is selected when either is absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100