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
In #74091 I had to mute @typescript-eslint/naming-convention rule manually for CSS classes created in react components because they don't abide by the regular JS naming convention. Examples:
We need to find a solution to exclude such variables from the linting on the project level. For example, we could use a special prefix or a suffix to filter them out.
The text was updated successfully, but these errors were encountered:
In #74091 I had to mute
@typescript-eslint/naming-convention
rule manually for CSS classes created in react components because they don't abide by the regular JS naming convention. Examples:componentName__element--modifier
componentName__element__element
kibana/src/plugins/advanced_settings/public/management_app/components/form/form.tsx
Lines 339 to 340 in 903f0e6
We need to find a solution to exclude such variables from the linting on the project level. For example, we could use a special prefix or a suffix to filter them out.
The text was updated successfully, but these errors were encountered: