Remove Style Note

https://github.com/freeCodeCamp/freeCodeCamp/issues/45487

I see here that we are intentionally supporting confusing but technically correct syntax. In light of this, we should remove the note here

https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/basic-javascript/access-array-data-with-indexes

Note: There shouldn’t be any spaces between the array name and the square brackets, like array [0]. Although JavaScript is able to process this correctly, this may confuse other programmers reading your code.

---

myFunction (args);
myArray [0];
myString [0];

All of these are non-standard things that technically work but nobody actually does in practice. We should either go out of our way to support this sort of thing or not. If we are going out of our way to support this sort of thing, then there really isn’t much point of letting the users know that it’s unconventional syntax.

See also: https://github.com/freeCodeCamp/freeCodeCamp/issues/45570

---

Personally, I think it’s valuable to teach the learners how to write code that others expect to see so that it’s easier for them to get hired, but we really need to be consistent. We should either help them with conventions or not bother. If we aren’t doing anything after making the note, then it’s just visual noise and should be removed.

[raisedadead]

Thanks for the thoughts @jeremylt & @bbsmooth

Here is what we should do:

1. Remove the note. IMHO you all are correct in assuming it does nothing other than draw attention to a confusing notion.
2. We should support the technically correct syntax (ignore testing for it, if we are).
3. Autoformatting may be a good idea, but I am afraid of accidentally introducing something else.

[ojeytonwilliams]

For what it’s worth here’s what I think about formatting. In practice the likes of prettier have rendered manual formatting unnecessary and unhelpful - I don’t need to see diff noise obscuring actual code changes.

If we’re overly picky about formatting then I can see that creating a frustrating experience. However, we should provide nicely formatted code in the examples. That way learners can pick up good habits simply by copying.