forked from cerc-io/snowballtools-base
306d3235b3
### TL;DR Reordered the properties in the `ProjectSearchBar` component to follow better coding standards. ### What changed? In `ProjectSearchBarDialog.tsx`, the 'getItemProps' object was moved to the end of the properties list within `ProjectSearchBarItem`. ### How to test? Verify that the `ProjectSearchBar` component functions as intended and that no properties are unduly affected by this change. ### Why make this change? This change enhances code readability and consistency, aligning the ordering of the properties more accurately with our standards. |
||
---|---|---|
.. | ||
.storybook | ||
public | ||
src | ||
.env.example | ||
.eslintrc.cjs | ||
.gitignore | ||
.node-version | ||
.prettierignore | ||
.prettierrc.json | ||
chromatic.config.json | ||
index.html | ||
package.json | ||
postcss.config.js | ||
README.md | ||
reload-dev.sh | ||
tailwind.config.js | ||
tsconfig.json | ||
tsconfig.node.json | ||
vite.config.ts |
React + TypeScript + Vite
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
Expanding the ESLint configuration
If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:
- Configure the top-level
parserOptions
property like this:
export default {
// other rules...
parserOptions: {
ecmaVersion: 'latest',
sourceType: 'module',
project: ['./tsconfig.json', './tsconfig.node.json'],
tsconfigRootDir: __dirname,
},
};
- Replace
plugin:@typescript-eslint/recommended
toplugin:@typescript-eslint/recommended-type-checked
orplugin:@typescript-eslint/strict-type-checked
- Optionally add
plugin:@typescript-eslint/stylistic-type-checked
- Install eslint-plugin-react and add
plugin:react/recommended
&plugin:react/jsx-runtime
to theextends
list