-
Notifications
You must be signed in to change notification settings - Fork 591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it worth detecting common error of unescaped ${aws:...}
?
#460
Comments
Imo yes, as I was even questioning if I was doing something wrong but had no idea what to search for. And as such, failed when I did search. |
#462 improved the diagnostic message and hashicorp/terraform-ls#463 will bring that change into the language server / VS Code. With that in mind I'm closing this issue. |
Awesome thank you @radeksimko and @apparentlymart! Greatly appreciated! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that users keep running into this problem despite our best efforts in documenting it:
hashicorp/terraform-ls#455
Is it worth adding some context to that error message in cases where we scan
:
afteraws
?The text was updated successfully, but these errors were encountered: