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
When using alloy fmt to validate a config and there is a syntax value, sometimes the line number is not helpful enough to find the issue. This is because many times the config is composed from many config files. Here's how it looks today:
This is a good idea. I put it on our proposal queue because I think it needs some consideration for whether doing this by default might break existing editor integrations or make stderr harder to parse for tools.
Without putting more thought into whether a change could break things, my default stance would be to make this opt-in with a flag.
Request
When using
alloy fmt
to validate a config and there is a syntax value, sometimes the line number is not helpful enough to find the issue. This is because many times the config is composed from many config files. Here's how it looks today:It would be great if it would provide a few lines of context to help show where the issue is. Something like:
Use case
It would really help show where errors are, especially with composed configurations.
The text was updated successfully, but these errors were encountered: