Add @mention autocomplete in task description 👥
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- javascript, react
- Domain
- frontend
Research direction
Start by reading client/src/components/Task/TaskModal.jsx and locating how the task description is displayed and updated. Add the requested @mention suggestions there, using the provided team list as the initial source. Verify that typing @ shows matching suggestions and choosing one inserts the mention into the description.
Written by the indexing model from the issue text.
Description
Add @mention autocomplete in task description 👥
File: client/src/components/Task/TaskModal.jsx
You can type @name but nothing happens 💀
No autocomplete, no suggestions fr!!
Fix: show suggestion dropdown when @ typed:
const [mentionQuery, setMentionQuery] = useState('')
const [showSuggestions, setShowSuggestions] = useState(false)
const handleDescChange = (e) => {
const val = e.target.value
setForm({...form, description: val})
const lastWord = val.split(' ').pop()
if (lastWord.startsWith('@')) {
setMentionQuery(lastWord.slice(1))
setShowSuggestions(true)
} else {
setShowSuggestions(false)
}
}
// hardcode team members for now:
const TEAM = ['anoopcodehack', 'phisher01', 'omkarwarik02']
const suggestions = TEAM.filter(m =>
m.includes(mentionQuery)
)
{showSuggestions && suggestions.length > 0 && (
{suggestions.map(s => ( { const words = form.description.split(' ') words[words.length-1] = `@${s} ` setForm({...form, description: words.join(' ')}) setShowSuggestions(false) }} className="block w-full text-left px-3 py-2 text-xs text-[#888] hover:bg-[#2a2a2f]"> @{s} ))} )}~20 lines! No backend needed 🎯
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 105
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 28
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from anoopcodehack/DevBoard
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anoopcodehack/DevBoard#588 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
anoopcodehack/DevBoard#587 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
anoopcodehack/DevBoard#586 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anoopcodehack/DevBoard#584 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
anoopcodehack/DevBoard#583 ·
Maintainers usually reply within 1 day
All issues in anoopcodehack/DevBoard
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Deepak3699/Ai_Mentor#244 ·
Maintainers usually reply within 1 day
-
ci-install-db-tools stall-case tests flake: stalled apt-get can be killed before it logs its callOpeneffort:low model:light plan planner:opus-5-5 tests
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Bug 🐞
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mozilla-mobile/firefox-ios#35986 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
component:sight
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agentic-os-org/ANOLISA#6738 · 2 comments ·
Maintainers usually reply within 1 day