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
make it so that when custom check functions are defined, throw => failed the file check and matches bad practice
maybe say:
throw new FoundBadPracticeError()
and
throw new FoundBestPracticeError()
or just make us return { passed: "false" / "true", reason:"x"} && declarative files -> if they look like that they fail due to following bad practice, different than custom which specifies exactly whether file passes or fails
then this would also let us have better error messages
why?:
clearer definition of custom-checks on bad practices
i keep wanting to throw an error if the file fails my check (i.e., throw error -> file is bad practice)
ability to display failure reasons on bad practice
critical
The text was updated successfully, but these errors were encountered:
make it so that when custom check functions are defined, throw => failed the file check and matches bad practice
maybe say:
throw new FoundBadPracticeError()
and
throw new FoundBestPracticeError()
or just make us return
{ passed: "false" / "true", reason:"x"}
&& declarative files -> if they look like that they fail due to following bad practice, different than custom which specifies exactly whether file passes or failsthen this would also let us have better error messages
why?:
The text was updated successfully, but these errors were encountered: