As we are working to add support for LWC, we would be very keen to hear any suggestions on LWC-specific rules that would be useful. Any ideas out there?
Is there scope to simply include the linter that comes with the standard LWC VsCode setup and pick up things that would pick up. I know it’s not very ‘Clayton’, but it might be a useful start.
It’s a fair point, and we must definitely consider it. The only reason why this wasn’t done before, is that at the moment this would require a breaking changes in our internal API. We are in the process of redesigning our core engine - so we’ll definitely consider the possibility of plugging in third-party engines. Thanks for sharing this @robert.baillie