Yeah if you look at the CustomJS code property you can see some bad escapes:
All the \\n should presumably be real newlines, i.e. just \n. Basically this code text is being escaped twice now.
That’s the problem [1], but I am not sure how best to fix it.
Once it looks like all of the outputs are being converted correctly, then I’ll run it on the full database.
Got it, that seems like a much more maintainable path ![]()
Well that’s a problem, we can hope it’s also the only problem! ↩︎
