Freecodecamp: [beta] Flexbox challenge 5 issue - similar to issue #12866
[beta] similar to issue #12866
This is an important issue, because the divs are too large you can only see one color in the Solution Window (the phone).... and thus cannot discern that there are other boxes (or child elements).
Because the challenge ends and a modal pops up, you cannot learn from the Solution and see the difference between a flex-direction:row or a flex-direction: column
Css Flexbox: Using the Flex-direction Property to Make a Column
http://beta.freecodecamp.com/en/challenges/css-flexbox/using-the-flexdirection-property-to-make-a-column
tommygebru
All 3 comments
@tommygebru Hey man! Wow, you are killing it in reporting these issues, appreciate your hard work.
However, since many of these issues are very similar and related to the same section, do you think you would be able to perhaps condense all of these into one issue (at least all of the related ones) and create a checklist so that they can be better organized and easier to attack once we start getting PRs in for these?
A good example of this would be an issue like #12698. This would be super helpful if you're up to it (as I realize you've already done a bunch of work by reporting these in the first place), especially since we have so many other issues coming in as well.
What do you think? Thanks again for helping out with beta!
no-stack-dub-sack
on 26 Jan 2017
Wow very cool @no-stack-dub-sack as you can see I tired myself out and decided to spend the day tackling personal projects, I will be back tomorrow to contribute, after some good sleep!
tommygebru
on 27 Jan 2017
@tommygebru sounds great! thanks!
no-stack-dub-sack
on 27 Jan 2017
Related issues
MichaelLeeHobbs
路
3Comments
danielonodje
路
3Comments
bagrounds
路
3Comments
DaphnisM
路
3Comments
MelissaManning
路
3Comments
Most helpful comment
@tommygebru Hey man! Wow, you are killing it in reporting these issues, appreciate your hard work.
However, since many of these issues are very similar and related to the same section, do you think you would be able to perhaps condense all of these into one issue (at least all of the related ones) and create a checklist so that they can be better organized and easier to attack once we start getting PRs in for these?
A good example of this would be an issue like #12698. This would be super helpful if you're up to it (as I realize you've already done a bunch of work by reporting these in the first place), especially since we have so many other issues coming in as well.
What do you think? Thanks again for helping out with beta!