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
Many contributors add tests with only line: 4 for reported errors. Often, the test cases should include the column and end position though. This could be enforced with a new ESLint rule that requires all of line, endLine, column, and endColumn to be present for all expected errors.
The text was updated successfully, but these errors were encountered:
FloEdelmann
changed the title
New rule require-positions
New rule require-error-positionsJul 8, 2024
Currently, there is no rule enforcing the structure of error objects. I am considering introducing a rule that developers can configure to enforce which properties (such as line, endLine, column, and endColumn) must be present in error objects. Additionally, this rule could specify whether the properties must follow a certain order. Of course, this will require a more detailed and specific design.
Many contributors add tests with only
line: 4
for reported errors. Often, the test cases should include the column and end position though. This could be enforced with a new ESLint rule that requires all ofline
,endLine
,column
, andendColumn
to be present for all expected errors.The text was updated successfully, but these errors were encountered: