stricklandrbls opened a new issue, #878:
URL: https://github.com/apache/daffodil-vscode/issues/878

   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.
   
   <details><summary><h3>Screenshot of TS errors</h3></summary>
   
   
![image](https://github.com/apache/daffodil-vscode/assets/30351915/e1900c19-03f9-430f-aa85-b9b9d66ed103)
   
   </details>
   
   **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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to