Understanding Notification Providers
A notification provider implements methods to show and hide notifications:Quick Setup
@refinedev/antd@refinedev/mui@refinedev/mantine@refinedev/chakra-uiAutomatic Notifications
Refine automatically shows notifications for CRUD operations:Create Operations
Update Operations
Delete Operations
Error Notifications
Automatic error notifications on failure:Custom Notifications
Using useNotification
Closing Notifications
Customizing Automatic Notifications
Success Notifications
Error Notifications
Disable Notifications
Undoable Notifications
For undoable mutations, show progress notifications:Custom Undoable Component
Advanced Patterns
Notification Queue
Grouped Notifications
Persistent Notifications
Action Notifications
Loading Notifications
Position and Styling
Notification Position
Custom Styling
Dark Mode
Testing
Mock Notification Provider
E2E Tests
Best Practices
- Keep messages concise - Users should understand at a glance
- Use appropriate types - success, error, warning, info
- Provide context - Include relevant details in description
- Set reasonable timeouts - 3-5 seconds for most notifications
- Don’t overuse - Too many notifications are annoying
- Make them dismissible - Let users close notifications
- Group related notifications - Combine multiple similar messages
- Use undoable for destructive actions - Give users a chance to revert
Common Patterns
Bulk Operation Notifications
Form Validation Notifications
Connection Status
Next Steps
- Learn about Forms
- Explore Real-time Updates
- Discover Authentication