The CI currently only runs the code to generate space accessor types, eslint, and dtslint. But the tests of the library itself are never actually checked automatically. Would it be a good idea to add npm run test to the CI, either by updating the lint:ci script or adding another step to the workflow?
The CI currently only runs the code to generate space accessor types, eslint, and dtslint. But the tests of the library itself are never actually checked automatically. Would it be a good idea to add
npm run testto the CI, either by updating thelint:ciscript or adding another step to the workflow?