Handle .sass file extensions

[WossomGonzo]

Hi, I wanted to use .sass files in my project and I noticed that they aren't handled correctly in sass-bundle.

It is easily fixed by adding:

        if (str_contains($path, '.sass')) {
            return str_replace('.sass', '.css', $path);
        }

In line 27 of sass-bundle/src/AssetMapper/SassPublicPathAssetPathResolver.php
And in line 45 in the same file

[bocharsky-bw]

That file resolves Sass file paths to Css ones so they can be used in the browser, otherwise, browsers can't handle the Scss, right? I'm not sure what you're doing or what exactly you need. If you could explain your case in more detail - it would help a lot.

[WossomGonzo]

That file resolves Sass file paths to Css ones so they can be used in the browser, otherwise, browsers can't handle the Scss, right? I'm not sure what you're doing or what exactly you need. If you could explain your case in more detail - it would help a lot.

Hi! Yes, let me explain my situation:

I'm using sass-bundle to write SASS code (the indented syntax), not SCSS. Because of that, all my stylesheets use the .sass file extension.

The issue is that, although the files are successfully compiled into CSS, the output files still retain the .sass extension instead of changing to .css. As a result, the web server serves them with the text/plain MIME type instead of text/css, and browsers ignore them entirely.

[bocharsky-bw]

Hey @WossomGonzo ,

Sorry for the delay! I see the problem now. Yeah, I think this bundle was initially written with SCSS files in mind. I suppose you can't just rename your .sass files into .scss because they have a slightly different syntax. If so, then the only way I see is to change the code base of this bundle in order to add the .sass support as well. I see you said it compiles those files into css successfully, so the problem is just in the output file name. Should be an easy fix I think. Do you want to create a PR to fix this?