3 ms·
Most are that good, or better. I actually debated putting that error because it's one that doesn't have a "help:" line that actively suggests how to fix it. So
by shepmaster 7y ago
Most are that good, or better. I actually debated putting that error because it's one that doesn't have a "help:" line that actively suggests how to fix it.
Some errors are admittedly worse, and people like estebank are actively working on improving them.
- estebank 7y agoFWIW, I think it was a good choice to showcase the underlying feature as opposed to showing off the diagnostics :)
- carapace 7y agoYou're the author of the blog post? Dunno if this is something you care about, but with JS turned off the code boxes are omitted (with no placeholders or other clues that something is missing.)
- shepmaster 7y agoI am! It's something I care about, but not sure if there's something I can do about it. The code blocks are powered by a `<script>` tag from GitHub's Gists. Unfortunately, I don't have the ability to edit that post without Wordpress completely removing those tags (I don't have appropriate permissions). I can ask for them to put `<noscript>` tags, but don't know if that will really help.