You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our custom Eslint rules are written in Typescript and must be built before Eslint and VSCode can use them.
Currently, the rules are built as a tgz file (eslint-plugin-twenty.tgz) to ensure they work from project installation.
This issue aims to leverage Nx's "workspace lint rules" feature (see https://nx.dev/nx-api/eslint/generators/workspace-rule) and how we can use it in our project, so we can avoid building a tgz file and still dynamically load eslint rules written in TS.
Technical inputs
Use Nx's generator to recreate the existing custom rules from eslint-plugin-twenty and load them in twenty-front's eslint config.
Configure an extendable eslint config at the root of the workspace, to set common base rules for all packages.
Use Nx's eslint plugin to set recommended configs.
Scope & Context
Our custom Eslint rules are written in Typescript and must be built before Eslint and VSCode can use them.
Currently, the rules are built as a
tgz
file (eslint-plugin-twenty.tgz
) to ensure they work from project installation.This issue aims to leverage Nx's "workspace lint rules" feature (see https://nx.dev/nx-api/eslint/generators/workspace-rule) and how we can use it in our project, so we can avoid building a
tgz
file and still dynamically load eslint rules written in TS.Technical inputs
eslint-plugin-twenty
and load them intwenty-front
's eslint config.tools/eslint-rules
andpackages/twenty-front
packages works.The text was updated successfully, but these errors were encountered: