Freecodecamp: Deprecated property grid-gap

[SimonSiefke]

[mstva]

Hello, @SimonSiefke is this still open to solve it or what?

[RandellDawson]

@Mstava At this point, nothing has been agreed upon on how to move forward, so there is no point in creating a PR yet.

[thecodingaviator]

My way of tackling this would be to teach both properties in the same challenge and add a note saying that grid-gap was the old way of doing it

[raisedadead]

People should not be taught the legacy property only because Safari doesn't support it yet.

Take away this and only this from any discussion, we need not be opinionated about what people 'need' to learn. The above argument is 100% opinionated. We need to teach facts, with disclaimers if needed and let users decide what they would like to learn, use or skip.

I will recommend let's keep the thread constructive with proposals on what would be a better solution.

Mine would be teach both the things, with correct disclaimers.

[RandellDawson]

@SimonSiefke Since grid-gap has not been deprecated, I vote for your option b. As with most things in the coding world, there are typically multiple ways of doing the same thing.

The best thing about the curriculum is that we can update it to something else at a later date. If at some point all relevant browsers can use gap, then we can change the challenge. My guess is by the time that happens, the new curriculum will be in place and it would only reference gap.

[RandellDawson]

I have always been under the impression that deprecated means no longer supported. I see nothing in the documentation which states grid-gap is no longer supported. If I am mistaken, please supply documentation stating so. If not, why do you say it is deprecated?

[raisedadead]

Since this discussion is not getting any constructive with same points coming over and again, here is what we are going to do:

• We will wait for 15 days from this comment for any additional interest in this thread (other members that currently involved in the discussion).
• Once it picks up at least 3-4 additional users and/or experts we can do a vote on the content changes.

Until then this thread should stand closed for discussions (issue to be left open).

[raisedadead]

Hi @SimonSiefke thanks for your feedback, I have marked the previous comment off topic. Here is our code of conduct, I would request you to be constructive, polite and succinct failing which we will have to enforce the COC.

[thecodingaviator]

Option b sounds good to me too.

[mstva]

As with most things in the coding world, there are typically multiple ways of doing the same thing.

I agree with this option, we could add multiple ways and let the user choose what to use @RandellDawson @raisedadead

[moT01]

Closing this as stale. If anyone wants to continue the discussion, I recommend creating a new issue so it might get some attention. Thanks and happy coding 🎉