{"action":"created","issue":{"url":"https://api.github.com/repos/sensational/sassphp/issues/3","labels_url":"https://api.github.com/repos/sensational/sassphp/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/sensational/sassphp/issues/3/comments","events_url":"https://api.github.com/repos/sensational/sassphp/issues/3/events","html_url":"https://github.com/sensational/sassphp/issues/3","id":44567863,"number":3,"title":"Support for Source Maps","user":{"login":"cuchac","id":165461,"avatar_url":"https://avatars.githubusercontent.com/u/165461?v=3","gravatar_id":"","url":"https://api.github.com/users/cuchac","html_url":"https://github.com/cuchac","followers_url":"https://api.github.com/users/cuchac/followers","following_url":"https://api.github.com/users/cuchac/following{/other_user}","gists_url":"https://api.github.com/users/cuchac/gists{/gist_id}","starred_url":"https://api.github.com/users/cuchac/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cuchac/subscriptions","organizations_url":"https://api.github.com/users/cuchac/orgs","repos_url":"https://api.github.com/users/cuchac/repos","events_url":"https://api.github.com/users/cuchac/events{/privacy}","received_events_url":"https://api.github.com/users/cuchac/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2014-10-01T14:13:18Z","updated_at":"2015-07-05T00:50:54Z","closed_at":null,"body":"I'm going to implement sourceMaps to sassphp. Is there any previous work related to this? I will also work on Sacy parts, so if you are connected with that project, is there any previous work on this?\r\n\r\nReply from @pilif:\r\n>I wrote 99% of sacy, so yeah. I'm familiar with that and I also was looking into source maps and let me tell you: There are challenges ahead:\r\n>\r\n>* Due to the way how sacy currently works, it really wants to feed the to-be-transformed content to the processor as a big string. When using libsass, this would be done using Sass::compile() and when using the ruby sassc, this is done using stdin. At least in the case of sassc, you can't have source maps when using stdin.\r\n>* This also means that at the time when you run the sass compilation, the information what source file the data came from is not available any more, especially when you use sacy with the merge_tags feature (which you will want to use if you want to have globally available mixins). As such, you won't get any meaningful mapping to the original file.\r\n>\r\n>If you have ideas on how to work around these issues, I'd be excited to have a look at an eventual Pull Request, but all approaches I tried so far were less than optimal in their outcome."},"comment":{"url":"https://api.github.com/repos/sensational/sassphp/issues/comments/118567792","html_url":"https://github.com/sensational/sassphp/issues/3#issuecomment-118567792","issue_url":"https://api.github.com/repos/sensational/sassphp/issues/3","id":118567792,"user":{"login":"absalomedia","id":3776787,"avatar_url":"https://avatars.githubusercontent.com/u/3776787?v=3","gravatar_id":"","url":"https://api.github.com/users/absalomedia","html_url":"https://github.com/absalomedia","followers_url":"https://api.github.com/users/absalomedia/followers","following_url":"https://api.github.com/users/absalomedia/following{/other_user}","gists_url":"https://api.github.com/users/absalomedia/gists{/gist_id}","starred_url":"https://api.github.com/users/absalomedia/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/absalomedia/subscriptions","organizations_url":"https://api.github.com/users/absalomedia/orgs","repos_url":"https://api.github.com/users/absalomedia/repos","events_url":"https://api.github.com/users/absalomedia/events{/privacy}","received_events_url":"https://api.github.com/users/absalomedia/received_events","type":"User","site_admin":false},"created_at":"2015-07-05T00:50:54Z","updated_at":"2015-07-05T00:50:54Z","body":"The only reason I've been having to get source maps / comments into sassphp is due to demands in my day job as there are project dependencies requiring SASS source map generation on the fly.\r\n\r\nThe aim has been to get 100% SASS coverage for the design teams I work with. As 3.2.x is close to that coverage I'm actually working on it less. \r\n\r\nHHVM compatibility for sassphp in my own build is just a far future concept I'm considering at the moment as the projects I'm with are considering long term deployment with HHVM."}}