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
As discovered in #110422 and currently being fixed in #151023, it's very easy to mess up ESLint rules so that they no longer trigger and there's no way to know obvious indication of the regression.
We should create tests to ensure that the expected validation errors actually do occur. To achieve this we can use this plugin which is already loaded in our ESLint config. This is similar to how @ts-expect-error works.
Example usage where ESLint will produce an error if the no-restricted-imports error isn't produced:
As discovered in #110422 and currently being fixed in #151023, it's very easy to mess up ESLint rules so that they no longer trigger and there's no way to know obvious indication of the regression.
We should create tests to ensure that the expected validation errors actually do occur. To achieve this we can use this plugin which is already loaded in our ESLint config. This is similar to how
@ts-expect-error
works.Example usage where ESLint will produce an error if the
no-restricted-imports
error isn't produced:(I've assigned myself because I've already have a working implementation of this locally which just needs some final touches)
The text was updated successfully, but these errors were encountered: