When single file components are used (which are either a single .bxm or .cfm file), the models/SingleFileComponentBuilder.cfc component is responsible for parsing the file and creating separate class and template files, which are then used to process the wire as usual. The problem is that if an exception occurs within the wire or processing of the template, the stacktrace is not very helpful to developers because it doesn't accurately tell what line the error was thrown on and the stack trace itself is confusing. We are limited in that none of the CFML or BoxLang engines allow us to overwrite the stack trace.
We need to come up with ideas for how to improve the developer experience with this.
When single file components are used (which are either a single .bxm or .cfm file), the models/SingleFileComponentBuilder.cfc component is responsible for parsing the file and creating separate class and template files, which are then used to process the wire as usual. The problem is that if an exception occurs within the wire or processing of the template, the stacktrace is not very helpful to developers because it doesn't accurately tell what line the error was thrown on and the stack trace itself is confusing. We are limited in that none of the CFML or BoxLang engines allow us to overwrite the stack trace.
We need to come up with ideas for how to improve the developer experience with this.