Skip to content
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

Stop using Sass glob importing #797

Merged
merged 1 commit into from
Apr 4, 2017
Merged

Stop using Sass glob importing #797

merged 1 commit into from
Apr 4, 2017

Conversation

tysongach
Copy link
Contributor

Glob importing is a feature of sass-rails. It makes for cleanly and
easily importing lots of partials, but it completely hides Sass errors.

For example, when you miss a semicolon and your Sass doesn't compile,
using glob imports with sass-rails you simply see an application error:
"We're sorry, but something went wrong."

But when using standard Sass imports, this error is an actual syntax
error, which provides helpful messaging ("Invalid CSS after…"), and
traces back to the source where the error was introduced.

Before

screen shot 2017-03-24 at 14 49 48

After

screen shot 2017-03-24 at 14 50 07

Glob importing is a feature of sass-rails. It makes for cleanly and
easily importing lots of partials, but it completely hides Sass errors.

For example, when you miss a semicolon and your Sass doesn't compile,
using glob imports with sass-rails you simply see an application error:
"We're sorry, but something went wrong."

But when using standard Sass imports, this error is an actual syntax
error, which provides helpful messaging ("Invalid CSS after…"), and
traces back to the source where the error was introduced.
@BenMorganIO BenMorganIO self-requested a review April 4, 2017 18:32
@nickcharlton nickcharlton merged commit ba613ad into master Apr 4, 2017
@nickcharlton nickcharlton deleted the tg-sass-imports branch April 4, 2017 19:16
iarie pushed a commit to iarie/administrate that referenced this pull request Jun 17, 2017
Glob importing is a feature of sass-rails. It makes for cleanly and
easily importing lots of partials, but it completely hides Sass errors.

For example, when you miss a semicolon and your Sass doesn't compile,
using glob imports with sass-rails you simply see an application error:
"We're sorry, but something went wrong."

But when using standard Sass imports, this error is an actual syntax
error, which provides helpful messaging ("Invalid CSS after…"), and
traces back to the source where the error was introduced.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants