Eugene ONeill

@arkhi, the API is changing and this may cause some confusion with existing documentation. If you're using 0.7.x (current release is 0.7.1) or earlier, you're going to use either: ```...

@georeith thanks for the feedback, we're trying to get things cleaned up and in a better state. In the meantime, have you read through the documentation on [Working with assets](https://github.com/sass-eyeglass/eyeglass#working-with-assets)?...

To be honest, I'm not entirely sure myself. I haven't really worked with assets in eyeglass yet and I'm not all that familiar with the implementation. What I know comes...

consider using the [true](https://github.com/ericam/true) extension for this

We use side-effect functions for things like updating config settings and do just about exactly what @davidkpiano describes. We then expose a mixin that does... ``` scss @mixin set-config(...) {...

Here's a slightly more complex example that might demonstrate the idea @chriseppstein and I have tossed around... ``` scss // allows us to keep a store of component definitions $component-store:...

What work needs to happen for this to land without the `BROWSERIFY_TESTS` flag? This has bitten us a few times and it's potentially a blocking issue for our build environment....

Thanks for the feedback and the great suggestion. I definitely want to support this. I opted not to make this a doc syntax as I want to eventually integrate the...

Yeah, completely agree. In my original implementation, I was doing something like ``` scss // a function that does something // @param {Color} $color [red] the color of something... @function...

Unfortunately, this isn't very likely to happen on my end anytime soon. I haven't had any time to work on this (it was a quick, thrown together in a weekend...