-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When compiling Sass, it is reading both local and global settings #44
Comments
Also, deleting the ../css folder seems to fix it. But, just entering the global settings without saving anything or applying changes to the current files makes the ../css folder again and compiles the style.css file in there, and in the selected project's settings folder. Compiling it a second time without deleting the folder makes the style-ck.css file, but it compiles on the 3 locations: /public/style.css, ../css/style.css and ../css/style-ck.css. This is the codekit3.config file relevant to this: "languageDefaultsSASS": {
"autoOutputAction": 0,
"autoOutputPathFilenamePattern": "*.css",
"autoOutputPathRelativePath": "\/public\/css",
"autoOutputPathReplace1": "sass",
"autoOutputPathReplace2": "css",
"autoOutputPathStyle": 1,
"createSourceMap": 0,
"debugStyle": 0,
"decimalPrecision": 10,
"outputStyle": 3,
"shouldRunAutoprefixer": 0,
"shouldRunBless": 0,
"useLibsass": 1
},
"\/public\/css\/style.css": {
"fileType": 16,
"inputAbbreviatedPath": "\/public\/css\/style.css",
"outputAbbreviatedPath": "\/public\/css\/style-ck.css",
"outputAction": 1,
"outputFlags": 0,
"shouldRunAutoprefixer": 0,
"shouldRunBless": 0
}, |
In your "steps to reproduce", did you click the "Apply Changes to Existing Files" button after modifying your project settings? If not, the existing files in the project did NOT adopt the new output paths; they would still have been using whatever output paths were set before you changed the project settings—likely the global defaults for new projects. |
I did, that's why I copied the codekit3.config stuff, it is already in the config that it should do that. Also, talking about that button, it doesn't give any feedback at all, it looks weird. It appears like it is only being pressed but it doesn't really work (really quick focus state). And it looks like the style-ck.css it is processed as if the global's compiled file was the one being modified. |
It is not possible for CodeKit to "use the global settings". The defaults for new projects are never accessed once a project is created. They're used at the time a new project is added to the app without an existing config file. As such, I'm having trouble understanding this issue. I need a screencast walking me through the issue step-by-step, please. Thanks! |
Quick, short summary:
When the global path for Sass is ../css it uses it even if the project's settings are different.
I'm using the PHP Laravel framework, so the files are on /resources/assets/css/, and the compiled ones are on /public/css/. My Project's settings set they are on that folder relative to the project's root. While my global says they are relative to the file on ../css.
I changed the global's path to something else and it stopped doing double, but changing it back to ../css makes it compile it again on the global settings instead of the local files.
Expected results:
To compile the file only in the project's settings chosen path.
Actual results:
It makes TWO files on the folder ../css relative to the file, even when the project's settings say otherwise.
It made this two compiled files when my original file is named "style.scss":
When it should've only been on /public/css/style.css, and it keeps refreshing those 3 files.
This is also the file extract on the codekit3.config:
Exact steps to reproduce:
The text was updated successfully, but these errors were encountered: