Frontend Assignment Task of SPARKLEHOOD
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Babel for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:
export default tseslint.config({
extends: [
// Remove ...tseslint.configs.recommended and replace with this
...tseslint.configs.recommendedTypeChecked,
// Alternatively, use this for stricter rules
...tseslint.configs.strictTypeChecked,
// Optionally, add this for stylistic rules
...tseslint.configs.stylisticTypeChecked,
],
languageOptions: {
// other options...
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
},
})You can also install eslint-plugin-react-x and eslint-plugin-react-dom for React-specific lint rules:
// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'
export default tseslint.config({
plugins: {
// Add the react-x and react-dom plugins
'react-x': reactX,
'react-dom': reactDom,
},
rules: {
// other rules...
// Enable its recommended typescript rules
...reactX.configs['recommended-typescript'].rules,
...reactDom.configs.recommended.rules,
},
})- To require a password when deleting an incident, create a
.envfile in the project root with the following variable (do NOT commit secret values to your repo):
VITE_DELETE_PASSWORD=your-secret-password
-
For convenience a
.env.examplehas been added. Copy it to.envand replace the password value. -
The app reads
import.meta.env.VITE_DELETE_PASSWORDat build time. If the env var is not set, the delete button will fall back to a normal confirmation dialog. -
Hint: the password hint displayed in the UI is
NNNN(useful reminder).
When deploying to GitHub Pages, set the env variable only for local builds or CI; secrets in client-side apps are inherently visible to users, so use this only for lightweight protection.