There seems to be a lot of instances where strict types and values are not being implemented and the TS compiler is reporting them as errors in the console. The extension will still compile successfully and build the extension package / run a debug session. If there are errors that are being reported that are actual TS errors then no compilation should succeed.
This also makes it difficult to pinpoint areas of code when there is an actual error that's breaking the extension.
Screenshot of TS errors
Note: Errors only seem to be getting reported in VSCode after the TS intellisense has had a change to index through the file. Meaning, errors only get reported after opening a file to edit. I'm assuming this is an artifact from the build system moving completely towards webpack and some files were not opened and generated errors.
There seems to be a lot of instances where strict types and values are not being implemented and the TS compiler is reporting them as errors in the console. The extension will still compile successfully and build the extension package / run a debug session. If there are errors that are being reported that are actual TS errors then no compilation should succeed.
This also makes it difficult to pinpoint areas of code when there is an actual error that's breaking the extension.
Screenshot of TS errors
Note: Errors only seem to be getting reported in VSCode after the TS intellisense has had a change to index through the file. Meaning, errors only get reported after opening a file to edit. I'm assuming this is an artifact from the build system moving completely towards
webpackand some files were not opened and generated errors.