{"action":"created","issue":{"url":"https://api.github.com/repos/angular/sickle/issues/46","repository_url":"https://api.github.com/repos/angular/sickle","labels_url":"https://api.github.com/repos/angular/sickle/issues/46/labels{/name}","comments_url":"https://api.github.com/repos/angular/sickle/issues/46/comments","events_url":"https://api.github.com/repos/angular/sickle/issues/46/events","html_url":"https://github.com/angular/sickle/issues/46","id":131186459,"number":46,"title":"Transpiling causes confusing line numbers in output","user":{"login":"martine","id":3847,"avatar_url":"https://avatars.githubusercontent.com/u/3847?v=3","gravatar_id":"","url":"https://api.github.com/users/martine","html_url":"https://github.com/martine","followers_url":"https://api.github.com/users/martine/followers","following_url":"https://api.github.com/users/martine/following{/other_user}","gists_url":"https://api.github.com/users/martine/gists{/gist_id}","starred_url":"https://api.github.com/users/martine/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/martine/subscriptions","organizations_url":"https://api.github.com/users/martine/orgs","repos_url":"https://api.github.com/users/martine/repos","events_url":"https://api.github.com/users/martine/events{/privacy}","received_events_url":"https://api.github.com/users/martine/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-02-03T23:18:13Z","updated_at":"2016-02-12T18:47:19Z","closed_at":null,"body":"When using sickle, the compiler error messages you get are relative to the sickle output, which means that file offsets are wrong.\r\n\r\nOne idea is to ensure that sickle output has output lines in the same place as input lines, which means generating code that (for example) doesn't use newlines.  That at least makes line numbers line up.\r\n\r\nBut in cases where we generate a synthetic constructor there's not a particular line in the source we are modifying, so we may be forced to add a new to the source.  But maybe even then we could do a rule like \"stuff all synthetic code in one line in the very bottom of the class, right before the closing curly brace\"."},"comment":{"url":"https://api.github.com/repos/angular/sickle/issues/comments/183447072","html_url":"https://github.com/angular/sickle/issues/46#issuecomment-183447072","issue_url":"https://api.github.com/repos/angular/sickle/issues/46","id":183447072,"user":{"login":"martine","id":3847,"avatar_url":"https://avatars.githubusercontent.com/u/3847?v=3","gravatar_id":"","url":"https://api.github.com/users/martine","html_url":"https://github.com/martine","followers_url":"https://api.github.com/users/martine/followers","following_url":"https://api.github.com/users/martine/following{/other_user}","gists_url":"https://api.github.com/users/martine/gists{/gist_id}","starred_url":"https://api.github.com/users/martine/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/martine/subscriptions","organizations_url":"https://api.github.com/users/martine/orgs","repos_url":"https://api.github.com/users/martine/repos","events_url":"https://api.github.com/users/martine/events{/privacy}","received_events_url":"https://api.github.com/users/martine/received_events","type":"User","site_admin":false},"created_at":"2016-02-12T18:47:19Z","updated_at":"2016-02-12T18:47:19Z","body":"I think I'm going to fix this in the google-internal wrapper of the TypeScript compiler.  That means there's nothing for Sickle to do.  It's a little too bad that means that others will still have this problem... maybe in the future the TS API will let us inject sickle in a way that works better."}}