What's up with the UTIs that QLColorCode declares?

[saagarjha]

I was taking a look at the UTIs that QLColorCode has in its Info.plist and it there seem to be a bunch of dynamic UTIs:

QLColorCode/Info.plist

Line 29 in ef0eddd

<string>dyn.ah62d4rv4ge81g6pq</string>

Why aren't we just properly defining them and sticking them in UTIImportedTypeDeclarations? Plus, why don't we support files such as public.c-source or other common file types?

[hamiltont]

Related discussion - whomwah/qlstephen#87

[ideologysec]

it looks like this is what macOS does for files that it doesn't know what they are, were created by an application, and are not explicitly plaintext.

ie:

$ mdls -name kMDItemContentType /Users/user/Developer/example-repo/example.code-workspace
kMDItemContentType = "dyn.ah62d4rv4ge80g55eqy01s55wrr31a2pdqy"

and this is surely something I'd like to see QLColorCode (or qlstephen) support, since it's basically a YAML/JSON file.