shebang checks in BoxRunner don't nicely handle invalid file paths
Description
The BoxRunner just blindly passes the input from the CLI args into a method to check and see if it’s a valid file path and expand it, but if the input is actually code and has special characters, then this throws runtime exceptions which are not caught. Found this while trying to generate AST graphs from VSCode.
Activity
Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
The BoxRunner just blindly passes the input from the CLI args into a method to check and see if it’s a valid file path and expand it, but if the input is actually code and has special characters, then this throws runtime exceptions which are not caught. Found this while trying to generate AST graphs from VSCode.