sass variables inside local directory codekit

#Sass variables inside local directory codekit full

In this Hook, handlebars is called to compile the changed file at $CK_INPUT_PATH and it's told to write the output to $CK_OUTPUT_PATH.

The screenshot above shows these variables in action.

#Sass variables inside local directory codekit full

$CK_OUTPUT_PATH will be the full output path, as specified in CodeKit.$CK_INPUT_PATH will be the input path of the changed file.If your Hook is a Bash script, you can use two special environment variables to determine which file triggered the Hook: If your Hook targets a type of file that is not one of CodeKit's built-in languages, you should read Adding Custom Languages To CodeKit. For details, see Setting Output Paths & Actions. If the Output Action is set to Copy or Ignore, Hooks do not run. Your Hook will run only on files that have their Output Action set to Process/Compile. If your Hook targets filetypes for which CodeKit has built-in processing, your Hook always runs after CodeKit's built-in steps complete. Drag Hooks up or down in Project Settings to change that order. If a file triggers more than one Hook, the Hooks are run in top-down order. Likewise, if you use the Is operator, you must provide a full, matching string. If you use Begins With, keep in mind that input and output paths start with a leading slash. RegEx is slower than other matching operators and should be used only as a last resort. Invalid RegEx will cause your Hook to fail. Wildcards are not supported in any operator other than Matches RegEx. The 'Path From Disk Root' option refers to a file's full input path, starting at the root of your drive: /Macintosh HD/Users/john/documents/project/scripts/file.jsĪssuming 'project' is the folder you've added to CodeKit, then the 'Path From Project Root' would be: /scripts/file.jsĪll matching operators are case-insensitive and ignore diacritic marks ( é and e are the same.) Use the Rule Editor to tell CodeKit which files should trigger this Hook. Customize the name, choose the type of script your Hook will run (AppleScript or Bash), then define the rules for file-matching. Open the Project Settings area, then choose the Hooks category:Ĭlick the button to add a Hook. Your command becomes another processing step for files of that type. You provide a custom command in either Bash or AppleScript, then tell CodeKit which files should trigger that command. Hooks let you extend CodeKit to handle any kind of file.