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
AFAIR this was also reported by someone to node-sass (//cc @am11). Looks like we add absolute paths in one place and relative/resolved paths to the input file in the other. Will investigate next!
For your other question, you simply return it with some loaded content, like
This will then parse the content and report errors etc. with the url you have given. If more imports are found inside content, the previous path you can query will say http://example.org/foo.scss.
I gave it a try, but it's more complicated than I thought. Might give some more info here when I have time,. Will re-scope this to 3.2.1 for now (still marked experimental, so not release critical).
Hey @rodneyrehm! I merged some commits that should address IMO the issues with get_included_files. I'm going to close this for now, but feel free to re-open this or a new one if you think there are still some problems! Btw. thanks for your work on sass.link.js!
It seems the
included_files
(sass_context_get_included_files()
) content is not populated properly when theSass_Import
containscontents
.With the following FS:
And the source
I expect
sass_context_get_included_files()
to return[ "/sass/loadfile" ]
with the following importers:My expectation is met by the first two. But with the last one,
importer_file_content
, I get[ "testfile" ]
.While we're on the subject of importers and included_files, what should happen, were I to set an import_entry's path to
http://example.org/foo.scss
?The text was updated successfully, but these errors were encountered: