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
Extract compass #1291
Extract compass #1291
Conversation
If it's moved into it's own gem, why not change Since it's for v4 I think it's okay to break backwards-compatibility, it's easy to migrate and it'd look more elegant as all of the middleman extensions use that syntax. |
@Arcovion Seems like a good idea, if we decide to break backwards compat. |
…y on it to be pure Ruby
Ping @bhollis @karlfreeman |
I'll have some time to take a look next week - I'm excited about it! |
Same as @bhollis. Less is more 👍. |
This looks really great! I'm assuming the logic behind I would be a fan of requiring users to add it to their Gemfile. Compass is a framework, you wouldn't include Foundation by default, so why Compass. However, not including it by default would need an explanation during the upgrade notes. So can see both sides of it. 👍 |
@karlfreeman Correct. That's the way it currently works in stable as well. Same question for Sprockets too. I'd like to encourage folks to not use either as much, so maybe we pull it out and require a |
Changes Unknown when pulling 47bcafd on deprecate_compass into * on master*. |
@@ -0,0 +1,6 @@ | |||
require "middleman-core" | |||
|
|||
Middleman::Extensions.register(:compass) do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you register this with the auto_activate: :before_configuration
option, you won't need the AUTOLOAD_COMPASS
stuff.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good.
This is awesome. Good work extracting it! My main comment is the one around using the |
\o/ |
Really happy with this PR. Started by extracting Compass support into a
middleman-compass
extension, which required rewriting a bunch of features in Ruby (which we mostly already had) instead of relying on Compass. Lead to nice cleanups all around and heavy usage of the Inline Asset rewriting middleware.Once this is merged, I'll actually move
middleman-compass
into its own repo. The question is, do we reference it in the over-gemmiddleman
or require users to add it to their Gemfile?