Show "Saving..." indicator when task is being updated 💾
Maintainers usually reply within 2 days
@yashTomar272 is already working on this.
Since Sep 3, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- javascript, react
- Domain
- frontend
Research direction
Start with client/src/context/BoardContext.jsx, then inspect Dashboard.jsx to see how the context value is consumed and where the navbar is rendered. Add the saving state around task updates and expose it to the dashboard; done means the indicator appears during an update and disappears afterward, including when the request fails.
Written by the indexing model from the issue text.
Description
Show "Saving..." indicator when task is being updated 💾
File: client/src/context/BoardContext.jsx
Tasks update silently 💀
Users don't know if changes saved fr!!
Fix: add saving state to context:
const [saving, setSaving] = useState(false)
const updateTask = async (id, updates) => {
try {
setSaving(true)
const { data } = await axios.put(
/api/tasks/${id}, updates, authHeaders()
)
setTasks(prev => prev.map(t =>
t._id === id ? data : t
))
} catch (err) {
console.error(err)
throw err
} finally {
setSaving(false)
}
}
// expose saving in context value
// show in Dashboard.jsx navbar:
{saving && (
💾 saving...
)}
~10 lines across 2 files! 🎯
No backend needed!!
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 105
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 27
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
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
anoopcodehack/DevBoard#589 ·
Maintainers usually reply within 2 days
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anoopcodehack/DevBoard#588 ·
Maintainers usually reply within 2 days
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
anoopcodehack/DevBoard#587 ·
Maintainers usually reply within 2 days
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
anoopcodehack/DevBoard#586 ·
Maintainers usually reply within 2 days
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anoopcodehack/DevBoard#584 ·
Maintainers usually reply within 2 days
All issues in anoopcodehack/DevBoard
Similar issues
-
clawsweeper:needs-product-decision clawsweeper:needs-security-review clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:security issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
openclaw/openclaw#166870 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
⚠ needs intervention document structure changed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Bug pulumi/pulumi
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
uoftblueprint/canada-basketball#32 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
andromarces/agent-loops#571 ·
Maintainers usually reply within 1 day