You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is related to adding support for ECR files to ameba (here). Currently, there's no easy way to get line/column information about where an ECR syntax error is when calling ECR.process_string. One suggestion to fix this is to replace the generic raises with raising Crystal::SyntaxException, which is what the compiler currently uses to capture line/column/file information. Alternatively, there could be a rescue block added to process_string that re-raises with the line/column/file information, either would work.
The text was updated successfully, but these errors were encountered:
nobodywasishere
changed the title
ECR::Lexer#consume_control should raise Crystal::SyntaxException instead of just ExceptionECR::Lexer#consume_control should raise Crystal::SyntaxException instead of just ExceptionNov 24, 2024
nobodywasishere
changed the title
ECR::Lexer#consume_control should raise Crystal::SyntaxException instead of just ExceptionECR::Lexer#consume_control should raise Crystal::SyntaxException instead of ExceptionNov 24, 2024
This is related to adding support for ECR files to ameba (here). Currently, there's no easy way to get line/column information about where an ECR syntax error is when calling
ECR.process_string
. One suggestion to fix this is to replace the genericraise
s with raisingCrystal::SyntaxException
, which is what the compiler currently uses to capture line/column/file information. Alternatively, there could be a rescue block added toprocess_string
that re-raises with the line/column/file information, either would work.The text was updated successfully, but these errors were encountered: