# Description of Changes
- **What was changed**
- Added missing trailing semicolons across React components, utilities,
tests, and build/test configs to ensure consistent formatting.
- Normalized arrow-function assignments to end with semicolons (e.g.,
`const fn = () => { ... };`).
- Harmonized imports/exports and object literals in configuration files
to terminate statements with semicolons.
- Updated test setup files and mocks to consistently use semicolons.
- **Why the change was made**
- Aligns the codebase with ESLint/Prettier conventions to prevent
auto-format churn and avoid ASI (automatic semicolon insertion) edge
cases.
- Improves readability and produces cleaner diffs in future
contributions.
---
## Checklist
### General
- [ ] I have read the [Contribution
Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md)
- [ ] I have read the [Stirling-PDF Developer
Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/DeveloperGuide.md)
(if applicable)
- [ ] I have read the [How to add new languages to
Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md)
(if applicable)
- [ ] I have performed a self-review of my own code
- [ ] My changes generate no new warnings
### Documentation
- [ ] I have updated relevant docs on [Stirling-PDF's doc
repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/)
(if functionality has heavily changed)
- [ ] I have read the section [Add New Translation
Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags)
(for new translation tags only)
### UI Changes (if applicable)
- [ ] Screenshots or videos demonstrating the UI changes are attached
(e.g., as comments or direct attachments in the PR)
### Testing (if applicable)
- [ ] I have tested my changes locally. Refer to the [Testing
Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/DeveloperGuide.md#6-testing)
for more details.
---------
Co-authored-by: Reece Browne <74901996+reecebrowne@users.noreply.github.com>
36 lines
640 B
TypeScript
36 lines
640 B
TypeScript
import { Notification } from '@mantine/core';
|
|
import { useTranslation } from 'react-i18next';
|
|
|
|
export interface ErrorNotificationProps {
|
|
error: string | null;
|
|
onClose: () => void;
|
|
title?: string;
|
|
color?: string;
|
|
mb?: string;
|
|
}
|
|
|
|
const ErrorNotification = ({
|
|
error,
|
|
onClose,
|
|
title,
|
|
color = 'red',
|
|
mb = 'md'
|
|
}: ErrorNotificationProps) => {
|
|
const { t } = useTranslation();
|
|
|
|
if (!error) return null;
|
|
|
|
return (
|
|
<Notification
|
|
color={color}
|
|
title={title || t("error._value", "Error")}
|
|
onClose={onClose}
|
|
mb={mb}
|
|
>
|
|
{error}
|
|
</Notification>
|
|
);
|
|
};
|
|
|
|
export default ErrorNotification;
|