User blog comment:Kirkburn/Syntax highlighting - helping you read and write code/@comment-24473195-20150311093048

Here's some (early) feedback:

For modules/Javascript:


 * The script highlighting and on-the-fly error detection is  perfect. Don't EVER go back to the old way. :)
 * The colors of the syntax highlighting clash with the background, making it a bit harder to see. For example, the color for the "function" is very similar to the background.
 * Perhaps the tokens/operators could be bolded to make them clearer.
 * The function to collapse text is very useful, but there should probably be some way to collapse/un-collapse all modules/functions. This will make it easier to find a pesky function containing erroneous code.
 * Adding line error in footer - It would be nice to if the syntax checker also added a line at the bottom of the page indicating which line contains the error (like wikipedia). This helps to detect unnoticed errors before submitting.

For articles

Bug:


 * When the article is opened by entering the address  of "?action=edit" the syntax highlighting fails.

General:


 * Coloring - If a page consists of only tags, templates and tables. It becomes full of colors. Perhaps highlighting the keywords/tokens/tags would make more sense than highlighting the whole page.
 * Line numbers in articles/templates - It makes sense to add line numbers to general articles (at least in the source) because when debugging a buggy page or helping someone fix pages, it becomes very hard to reference a particular block of text. This is made worse in cases where a particular line of  "code" or wikitext is repeated, and it become completely impossible to reference those chaotic and long templates.

P.S. I hope that soup of colored lines in templates will make people annoyed enough to make them embrace the moon (LUA).