Grzegorz Rozdzialik

Sorry for the lack of activity, I did not see the issue You can either mention that import as a new import group in the rule configuration, or use the...

@pvinis Did you manage to come up with an example?

Unfortunately, there is no option to do that at the moment. However, it seems that you want the shims to be imported first, so the rule's configuration should mention that...

It seems to be doable. Here is a snippet that describes differences between different syntaxes for imports declarations: https://astexplorer.net/#/gist/adb7b38f4ffe0b54727c16ce654f0285/latest I can add a new configuration option for each `matching-rule` that...

@quezak Thank you for the suggestions and feedback 😄 > * you could describe in README that the order of `matching-groups` serves as priorities from top to bottom, I found...

Thanks for suggesting a feature. This tool was written to ignore only specific strictness-related error codes, not all errors from some files. Can you tell me what is your use...

I see. In this case, have you considered writing the library in JavaScript, if you don't need the typechecking? Anyway, it seems worth migrating to a different config format for...

Thanks for providing another possible use case for this feature. I am not opposed to adding such option to `loose-ts-check`. As for your use case, I would rethink whether such...

Hey, thanks for the contribution and bringing up these issues! I haven't tested loose-ts-check with newer TS versions, and it makes sense to do that. I will probably review it...

Yup, I agree, the tool should handle that case too. Thanks for checking