Currently we are having some indifferences with the packages that use the eslint-config's in this repository. Hence I would like to introduce some sort of testing, which is ensuring the configuration is still usable without any of the authors to require cloning/pulling the whole project, and testing new compatibility of the update libraries in the pull requests.
How to solve?
I would like to add a folder where we have failing and passing files, which individually will be automatically tested and then the CI can tell, if everything is fine, or not.
Motivation
Currently we are having some indifferences with the packages that use the eslint-config's in this repository. Hence I would like to introduce some sort of testing, which is ensuring the configuration is still usable without any of the authors to require cloning/pulling the whole project, and testing new compatibility of the update libraries in the pull requests.
How to solve?
I would like to add a folder where we have failing and passing files, which individually will be automatically tested and then the CI can tell, if everything is fine, or not.