Dashboard frontend uses old controller endpoint not the actual DashboardWidget implementation
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 738
- Forks
- 162
- Avg merge
- 6h 2m
- Merged PRs (30d)
- 35
Description
Was about to do some performance optimization of the hot paths in the item querying logic in the widget then I noticed something:
The dashboard widget is registered through DashboardWidget, but the rendered frontend still uses the old controller endpoint via the JS dashboard app. So DashboardWidget is not the sole implementation; it is the integration point, while NotesController::dashboard() is the data backend for the actual dashboard UI.
So we have two divergent implementations:
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
Read src/NotesService.js around lines 63-74, then compare the dashboard paths in lib/Controller/NotesController.php lines 114-142 and lib/AppInfo/DashboardWidget.php lines 80-113. Determine which implementation the rendered dashboard frontend should use and how the divergent logic can be consolidated. Done means the dashboard no longer relies on separate, inconsistent implementations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- backend, frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100