freeCodeCamp: Sass challenges don't work
Challenge storing-data-with-sass-variables has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36.
<style>
$text-color: red;
.header{
text-align: center;
}
.blog-post h2 {
color: $text-color;
}
</style>
<h1 class="header">Learn Sass</h1>
<div class="blog-post">
<h2>Some random title</h2>
<p>This is a paragraph with some random text in it</p>
</div>
<div class="blog-post">
<h2>Header #2</h2>
<p>Here is some more random text.</p>
</div>
<div class="blog-post">
<h2>Here is another header</h2>
<p>Even more random text within a paragraph</p>
</div>
Hello Everyone, I think I found a bug in the challenge Storing Data With Sass Variables. I think I did everything right, but the h2 and the .blog-post elements colour doesn’t change to red. I pass two of the user stories but not these: Your .blog-post element should have a color of red. Your h2 elements should have a color of red.
It also doesn’t change red. But it passes the user stories: Your code should have a Sass variable declared for $text-color with a value of red. Your code should use the $text-color variable to change the color for the .blog-post and h2 items
Thank you in advance, and the new things in Beta seem amazing keep up the great work! Can’t wait to work through more of them! 👍
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 7
- Comments: 39 (14 by maintainers)
You may add your color style to div tag. This works for me.
I’m going through the Sass lessons now. I’ll post any additional lessons that are broken.
The full list of Sass lessons with broken tests: https://learn.freecodecamp.org/front-end-libraries/sass/store-data-with-sass-variables https://learn.freecodecamp.org/front-end-libraries/sass/use-for-to-create-a-sass-loop https://learn.freecodecamp.org/front-end-libraries/sass/use-each-to-map-over-items-in-a-list https://learn.freecodecamp.org/front-end-libraries/sass/apply-a-style-until-a-condition-is-met-with-while
Here’s a visual aid:
I also have confirmed intermittent test passing (by spamming “Run the tests”) on: https://learn.freecodecamp.org/front-end-libraries/sass/store-data-with-sass-variables https://learn.freecodecamp.org/front-end-libraries/sass/use-each-to-map-over-items-in-a-list
but not on the other 2 broken Sass lessons (these always fail to pass): https://learn.freecodecamp.org/front-end-libraries/sass/use-for-to-create-a-sass-loop https://learn.freecodecamp.org/front-end-libraries/sass/apply-a-style-until-a-condition-is-met-with-while
@Azbo400 Thank you for reporting this issue. It looks like we don’t actually support compiling the Sass yet 😅
here trick for Sass: Use @for to Create a Sass Loop : there is no second chance because there is bug in this challenge for sure…
<style type='text/sass'> @for $j from 1 through 5 { .text-#{$j} { font-size: 10px* $j; } } </style>Hello
Hello
Hello
Hello
Hello
I agree that it’d be a good idea to warn people that Sass doesn’t work yet.
In the meanwhile, I recommend folks follow the Sass official page’s guide to installing a Sass compiler and following their guide (and / or FCC’s Sass tutorials) on their own machines. The guide starts here: http://sass-lang.com/install
Nope, still happening to me when I try the tests. Seem to only affect some users.
I struggled initially with same issues but so far I’ve got all to pass (up and including the @while example - not tried the others yet) - the issue seems to be white space For some e.g. the @while example even needed to remove any indenting of the SASS bit
Try deleting any blank lines between the code and - if that doesn’t solve it - not indenting the SASS code at all. [using FCC with Safari 11.0.2]
Hi all, whatever the issues are, they appear to be fix. Passed the challenge first time & i’m using Chrome Version 67.0.3396.87 (Official Build) (64-bit)
@MikeForde This worked for me when switching to Safari to get passed this one module. However, I still could not get it to work in any way while running it in Chrome 67.
Yeah. Its not working. Will there be any notification when it is fixed?