Do not transfer source files during build #143
Labels
conclusion: declined
Will not be worked on
topic: code
Related to content of the project itself
type: enhancement
Proposed improvement
I'm not entirely sure why the source files are being transferred into a temporary folder rather than just referencing their original locations but this does have some impacts to how modern IDEs treat the errors that come out during the compilation process. The code for the screenshots below can be found on my GitHub profile here if you need a sample.
It could be something you had originally used to service your IDE, which may still be needed. If so, this mechanism should be kept inside your IDE and not within the CLI. But rather have the CLI simply pointed at your temporary build folder generated by your IDE.
When issues occur within the compilation process many IDEs use the information in the out stream and error stream and parse it out so they can report those issues back to the developer through some easier means of locating them. In this sample I've intentionally misspelt the name of an enum to exhibit what would show up within VS Code.
You can see from the above screenshot that the compiler has detected the misspelling and reported it back to me. Normally I would simply be able to click on the link and it would take me directly to the file that caused the issue along with move me directly to the offending line to fix it.
The above error depicts what happens indicating the file was not found (which given it's temporary that's not surprising). However worse would be editing that other copy of the code rather than the real copy that is being managed within source control.
Fixing this and not transferring the code to a separate folder to build there should let the IDEs report back and allow their interfaces to work in the way they were intended.
The text was updated successfully, but these errors were encountered: