![Template literal with curly brace and newline triggers a 'semi-colon expected' error · Issue #88 · microsoft/typescript-styled-plugin · GitHub Template literal with curly brace and newline triggers a 'semi-colon expected' error · Issue #88 · microsoft/typescript-styled-plugin · GitHub](https://user-images.githubusercontent.com/6667278/50070705-10829f80-019d-11e9-8ce6-7f426b6de36a.png)
Template literal with curly brace and newline triggers a 'semi-colon expected' error · Issue #88 · microsoft/typescript-styled-plugin · GitHub
![Object-curly-newline for destructuring not working as expected in editor · Issue #9931 · eslint/eslint · GitHub Object-curly-newline for destructuring not working as expected in editor · Issue #9931 · eslint/eslint · GitHub](https://user-images.githubusercontent.com/6467349/35770411-a0c3c708-08e8-11e8-9a7f-487a5f5abb0e.png)
Object-curly-newline for destructuring not working as expected in editor · Issue #9931 · eslint/eslint · GitHub
![Ben Freundorfer on Twitter: "Another example... Totally get why the message makes sense from the JSON parser's perspective but to the user this might be more confusing than a simple "syntax error Ben Freundorfer on Twitter: "Another example... Totally get why the message makes sense from the JSON parser's perspective but to the user this might be more confusing than a simple "syntax error](https://pbs.twimg.com/media/FJpNZ9LWUAUu4F_.png)
Ben Freundorfer on Twitter: "Another example... Totally get why the message makes sense from the JSON parser's perspective but to the user this might be more confusing than a simple "syntax error
![Template literal with curly brace and newline triggers a 'semi-colon expected' error · Issue #88 · microsoft/typescript-styled-plugin · GitHub Template literal with curly brace and newline triggers a 'semi-colon expected' error · Issue #88 · microsoft/typescript-styled-plugin · GitHub](https://user-images.githubusercontent.com/6667278/50070732-2a23e700-019d-11e9-86b6-d7b67feaaef0.png)