Improve error reporting for single-file component exceptions #246

Copilot · 2025-11-25T06:24:07Z

Single-file components (.cfm/.bxm) are parsed into separate generated class and template files. When exceptions occur, stack traces reference these temp files, making it difficult to locate errors in the original source.

Changes

Source tracking in SingleFileComponentBuilder: Parse and track @startWire line number during file processing
Metadata injection in generated components: EmptySingleFileComponent.cfc/.bx now includes _singleFileSourcePath and _singleFileLineOffset variables
Error enhancement in Component.cfc:
- _isSingleFileComponent(), _getSingleFileSourcePath(), _getSingleFileLineOffset() - accessor methods
- _buildEnhancedErrorMessage() - constructs debug info with source file path and estimated line numbers
- Exception wrapping in _applyCalls(), _render(), and _withParams()

Example Output

When an error occurs in a single-file component:

Variable [UNDEFINED_VAR] is undefined

=== CBWIRE Single-File Component Debug Info ===
Original source file: /app/wires/MyComponent.cfm
Wire code starts at line: 8 in the original file
Estimated source line: ~15
================================================

Tests

Added unit tests for SingleFileComponentBuilder.parseContents() line tracking and Component single-file detection/error enhancement methods.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

www.ortussolutions.com
- Triggering command: /usr/bin/curl curl -s REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

This section details on the original issue you should resolve

<issue_title>Improve error reporting when exceptions occur on single file components/wires.</issue_title>
<issue_description>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. If 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.</issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes Improve error reporting when exceptions occur on single file components/wires. #245

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

github-actions · 2025-11-25T06:27:38Z