IRC transcript from 5/29/13

an awkward workflow

[09:34am] kwaleDesign: i'm working on a compass extension…specifically i'm making changes to that extension so i really want to be working in the output of that extension so that i have a compass watch set up and the directory structure of the output (not of the extension's directory). If i work directly in the extension, I can't easily run compass watch and process sass files, so if a mistake is made it isn't caught until i re build the gem, re install the gem, and run compass create…

[09:36am] kwaleDesign: so, my question is: what is the best workflow for working on a compass extension?

[09:51am] Snugug: kwaleDesign: Take a look at Breakpoint
[09:51am] Snugug: https://github.com/team-sass/breakpoint
[09:52am] Snugug: We've got a folder called "test" where we use 'add import path" to allow us to use our compass extensions as we develop
[09:52am] scottkellum: kwaleDesign: more specifically just add an import path to your extension instead of including the extension itself https://github.com/Team-Sass/breakpoint/blob/2.x.x/test/config.rb#L18
[09:52am] Snugug: Singularity does something similar https://github.com/Team-Sass/Singularity

[09:53am] Snugug: Thanks scottkellum
[09:53am] scottkellum: you should still test your gem before pushing
[09:54am] Snugug: Yup, and the way to do that is, after you've built your gem, run gem install {gem name} and it will install locally. From there, test with a new clear Compass project

[10:02am] kwaleDesign: Snugug++
[10:03am] kwaleDesign: looking into those suggestions now, thanks for the tips

[10:04am] kwaleDesign: scottkellum++
[10:05am] kwaleDesign: much appreciated guys, this appears to be what i need