Add loading and error feedback to settings NotificationRow toggle persistence

[Jagadeeshftw]

📌 Description

NotificationRow (src/features/settings/components/notifications/NotificationRow.tsx) toggles email/weekly preferences with no pending state and no error feedback if the save fails, and its aria-label lacks the "notification preference" context.

💡 Why it matters: Users can't tell whether a preference change saved or failed.

🧩 Requirements and context

• Disable the toggle and show a pending indicator while saving.
• Surface an error (and revert) if the save fails.
• Improve the toggle aria-label to describe the preference being changed.

Non-functional requirements

• Must be secure, tested, and documented.
• Should be efficient and easy to review.

🛠️ Suggested execution

1. Fork the repo and create a branch

git checkout -b feat/notificationrow-feedback

2. Implement changes

• Write/modify the relevant source: src/features/settings/components/notifications/NotificationRow.tsx
• Write comprehensive tests: src/features/settings/components/notifications/NotificationRow.test.tsx
• Add documentation: inline TSDoc
• Include TSDoc doc comments
• Validate security assumptions: n/a

3. Test and commit

• Run tests:

npm run test

• Cover edge cases: save success, save failure + revert, pending disable
• Include test output and security notes in the PR description.

Example commit message

feat(notifications): pending + error feedback on toggle row

✅ Acceptance criteria

• Toggle disabled + pending indicator while saving
• Error surfaced and state reverted on failure
• aria-label describes the preference
• Tests cover success/failure/pending

🔒 Security notes

None.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[Jacques-codes]

I've reviewed the issue and believe I can help resolve it. My plan would be to investigate the underlying cause, implement a maintainable fix, and verify the changes through comprehensive testing before submitting a pull request.

Feel free to assign it to me if it's still available.

[Glam26]

I'd love to work on this issue.

I enjoy tackling infrastructure and reliability-focused tasks, and this combines both in a way that's interesting. My approach will be to keep the implementation simple, well-documented, and easy to maintain while ensuring the acceptance criteria are fully covered.

I'll provide clear commits, tests for critical paths and edge cases, and regular progress updates throughout development.

[444notdotun]

Hi,

With 4 years of hands-on experience across backend, frontend, and smart contract development, I'm confident I can complete this task quickly and to a high standard. I've reviewed the requirements in detail and fully understand what's needed.

My focus is on writing clean, efficient, and maintainable code backed by thorough testing and industry best practices. I'll ensure the solution is production-ready and delivered on time.

I expect to have my PR ready in less than 10 hours.

[Johnpii1]

Hello Sir,

I came across your project and I’m really interested in contributing.

I have experience with React for building responsive, user-friendly interfaces, and I’m also familiar with smart contracts and blockchain basics. I focus on writing clean, scalable code and improving user experience.

I’m a fast learner and ready to get started immediately. Please let me know the next steps.

Thank you.

Best regards,
Johnpaul

[leocagli]

I've reviewed the issue and understand the scope. Please assign me so I can begin.

[grantfox-oss]

🦊 GrantFox — @Jacques-codes has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #194)
2. Your PR will be reviewed by the Grainlify maintainers

Good luck! Track your progress on GrantFox.