Greenstand / Greenstand/treetracker-admin-client
Should we order the candidates by distance?
Open
question
tool: Capture Matching
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 212
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue body names no files, tests, entry points, or acceptance criteria. Start by locating the admin panel view that displays candidate results and clarify whether ordering by distance is required, how distance is calculated, and what should happen when distance is unavailable. Done means the expected candidate ordering is defined and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100