Jake Worth

First Pull Request to SASS

March 24, 20142 min read

SASS bills itself as ‘the most mature, stable, and powerful professional grade CSS extension language in the world’. It’s called an ‘extension language’ of CSS because it augments the power of that language.

I’m grateful for SASS because it gives me more options as a developer. I wanted to contribute to the project and decided to focus on documentation.

To start work, I forked the SASS repo, cloned it to my machine, and installed the bundle.

Next, I ran the tests, which failed. When this happens, it’s tempting to assume that the build is broken, but that is rarely the case. More than likely my environment is not set up properly. I’ve found that it’s better to assume the build is green, because it usually is.

The failure message was ‘this method is depreciated’. From past experiences, this seemed Ruby-related. Sure enough, switching from Ruby 2.1.0 to Ruby 1.9.3 fixed it.

$ rvm use ruby-1.9.3-p448
$ bundle exec rake

1835 tests, 10923 assertions, 0 failures, 0 errors, 3 skips. ‘Skips’ are tests that aren’t written or I can’t run. The three skips provided the error message ‘can be run on Windows only’, which makes sense, given that I’m developing with Ubuntu.

I started out by fixing some random typos, and in the process found whitespace, which are trailing blank spaces. Whitespaces are ignored by the interpreter, but they should be avoided. I decided to pause and hunt down whitespace.

Many teams won’t accept commits that only remove whitespace, arguing that the gain of such an improvement is outweighed by the risk. A ‘whitespace commit’ can invalidate older pull requests and introduce bugs. There’s also an argument that as long as humans write code, whitespace will exist, and that removing it is a somewhat of a fool’s errand. I’m going to do it anyway, because I am also fixing misspellings.

I wanted a script to find and fix the whitespace. After some reading, I found this post and tweaked the command as such:

$ find . -type f -name '*.rb' -exec sed --in-place 's/[[:space:]]+$//' {} +

A breakdown:

  • find . - Search for files all in a directory hierarchy
  • type -f - Limit the search to regular files
  • -name ‘*.rb’ - Limit the search to files that end in ‘.rb’ (this prevents me from altering binary files)
  • -exec - Execute anything to the right of this command as a subprocess of the first (find’) command
  • sed - Use the stream editor, which finds and transforms text
  • —in-place - Edit the files in place
  • ‘s/[[:space:]]+$//’ {} + - Use this regular expression for the search, which finds any extra space at the end of a line or space on a line all by itself, removes it, then terminates the command

Scripts are powerful; don’t use them unless you know what they do.

This script found twelve instances of trailing whitespace, which I removed and committed to a new branch called ‘task/fixtyposand_whitespace’. On top of that I added twelve typo fixes.

Running the test suite again returned the same result, a decent assurance that I didn’t break anything. I pushed my changes to Github and opened this pull request. It was merged the next day. Thanks to the team at SASS for building a great project.

Jake Worth

I'm Jake Worth, a Chicago-based web developer. Blog About Now