The magic column [tagname] should handle number columns results gracefully

Question

The magic column [tagname] will decorate and auto link tag names when used in a query. This feature relies on the JavaScript processing in the browser. The client-side script assumes it will always get a string. Now try this query:

select id [tagname]
from votetypes

Id is an tinyint in SQL Server and becomes a JavaScript Number when the resultset is send over the wire.

The result is ... column headers only. Not a single row gets rendered. No errors in the UI. But that is a different story in the Developer Console of the browser.

In query.resultset.js the tagFormatter does this:

if (!value || !(value.match(/^[a-z0-9#.+-]+$/) || (isMultiTags = (value.search(/^(?:<[a-z0-9#.+-]+>)+$/) > -1)))) {
    return defaultFormatter(row, cell, value, column, context);
}

In the above snippet value will be of type Number and unfortunately Number doesn't have methods named match or search so it will fail there with a

Uncaught TypeError: value.match is not a function

(in the minified version the variable name is different).

I guess that if logic needs to include a typeof value !== 'string' so it will for Number columns fallback to the default formatter as it does for other case where it can't workout if the field has a supported tag name.

The workaround is simple: Only use string value columns with the magic column [tagname] to not break the client-side JavaScript.

This post is primarily meant to document the unexpected behavior. For a fix we wait for 6 to 8 weeks till soon™.