Improve debugability of error message for a malformed highlight tag

[leonardehrenfried]

I didn't add a test case since this change is tiny.

Is that ok or should I add a test that checks that the error message matches?

[mattr-]

Did you run the tests and do they still pass after your change? If so,
then I see no reason to test the contents of the error message.

However, if the condition that causes this error in the first place is
not covered, then I think it's appropriate to add another pull request
for that. The lack of a test case for the actual error shouldn't keep
this from being merged.

[leonardehrenfried]

I had one test failure before my commit

1) Failure: test: kramdown should convert quotes to smart quotes. (TestKramdown) [/Users/lenni/dev/jekyll/test/test_kramdown.rb:26]: <"<p>&ldquo;Pit&rsquo;hy&rdquo;</p>"> expected but was <"<p>&#8220;Pit&#8217;hy&#8221;</p>">.

and this one remains after the change. Since Travis runs the tests fine it seems that the failure is due to an outdated version of kramdown being installed on my machine by bundle install.

[mattr-]

Ok. Thanks for confirming. The new error message also looks fine as well.

👍 from me.

[mattr-]

@parkr or @mojombo any thoughts on this pull request?

[mattr-]

@Lenniboy you will most likely increase your chances of getting this merged if you put it on a feature branch and make sure it's up to date with the latest code in the master branch.

[parkr]

Looks good to me.