Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chore: config updates vscode tailwind eslint #14

Merged
merged 5 commits into from
Sep 21, 2024

Conversation

Zyruks
Copy link
Member

@Zyruks Zyruks commented Sep 21, 2024

Changes Made 🎉

  • Added .tool-versions to .gitignore:

    • Excluded version management files from being tracked in the repository.
  • Updated package.json:

    • Updated @commitlint/cli, @commitlint/config-conventional, and other related dependencies.
    • Simplified the prepare script by removing npx.
  • Updated .lintstagedrc:

    • Added manypkg fix for package.json to ensure workspace consistency.
    • Kept the existing Prettier and ESLint checks for JavaScript and TypeScript files.
  • Updated prettier.config.mjs:

    • Added support for Tailwind CSS functions like cn, clsx, and cva in the Prettier configuration.
    • Rearranged the plugin order for better formatting.
  • Updated .vscode/settings.json:

    • Enhanced Tailwind CSS support by including specific class attributes and languages for better autocompletion and linting.
    • Adjusted eslint settings to apply code actions more explicitly.

Describe Changes

This PR updates various configuration files to enhance development workflows:

  • Tailwind CSS support has been improved in VSCode with additional class attributes and language configurations.
  • ESLint settings have been updated for more explicit code actions on save.
  • Prettier configuration now supports custom Tailwind functions and has optimized plugin order.
  • Gitignore and lint-staged settings have been enhanced to improve workspace and package management.

Checklist ✅

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

- Added `.tool-versions` to `.gitignore` to exclude version management files from being tracked in the repository.
…ts in package.json

- Updated `@commitlint/cli` and `@commitlint/config-conventional` to version `^19.4.1` for the latest linting rules.
- Added `@commitlint/types` version `^19.0.3`.
- Upgraded `@ianvs/prettier-plugin-sort-imports` to version `^4.3.1` for better import sorting functionality.
- Updated `lint-staged` to version `^15.2.10` for improved compatibility.
- Simplified the `prepare` script from `npx husky install` to `husky`.
…r package.json

- Updated `.lintstagedrc` to run `manypkg fix` on `package.json` files to ensure workspace consistency.
- Retained existing Prettier and ESLint checks for `js`, `ts`, `jsx`, and `tsx` files.
…port

- Updated `prettier.config.mjs`:
  - Added `tailwindFunctions` array with support for `cn`, `clsx`, and `cva` functions.
  - Rearranged plugins to ensure proper execution order, placing `prettier-plugin-jsdoc` before `prettier-plugin-tailwindcss`.
- Retained all existing configurations for `importOrder`, JSDoc, and Tailwind settings.
… eslint fix actions

- Updated `.vscode/settings.json`:
  - Enhanced `tailwindCSS` support with `classAttributes` and `includeLanguages` for better class name autocompletion and linting.
  - Changed `source.fixAll.eslint` to "explicit" for more explicit code action saves.
  - Retained existing customizations for Prisma and general formatting settings.
@Zyruks Zyruks added the Type: Enhancement Suggest an improvement for an existing feature. label Sep 21, 2024
@Zyruks Zyruks self-assigned this Sep 21, 2024
@serudda serudda merged commit 91ab340 into main Sep 21, 2024
1 check passed
@serudda serudda deleted the chore/config-updates-vscode-tailwind-eslint branch September 21, 2024 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Suggest an improvement for an existing feature.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants