I've given up and just do this: `JSON.parse(respon...
# suitescriptm
michoel
12/17/2019, 12:26 AMI've given up and just do this:
JSON.parse(response.data.replace(/<!--(.*?)-->/g, ''))s
Seth Duda
12/19/2019, 4:00 AM@michoel I ran into this as well in the past. Here's how I found to fix it:
Seth Duda
12/19/2019, 4:00 AMcontext.response.setHeader({
name: 'Content-Type',
value: 'application/json',
});
context.response.write(...);
Seth Duda
12/19/2019, 4:02 AMIf you set the Content-Type to application/json, it stops adding the commented out block to the end of the response when the response contains some special keywords
m
michoel
12/19/2019, 4:25 AMI'm pretty sure I tried that, also I had it working for a while and one day it just broke without touching
s
Seth Duda
12/19/2019, 4:29 AMI haven't run into any issues so far with that approach
m
michoel
12/19/2019, 4:35 AMGood to know but to be honest I don't have much faith in NetSuite not breaking it again so I think I'll like the replace in my code for now
michoel
12/19/2019, 4:35 AMWhat do you mean by "contains some special keywords" though?
s
Seth Duda
12/19/2019, 4:40 AMfor example, if you return json like this without setting the Content-Type to application/json, no commented out block is added to the response by NS
Seth Duda
12/19/2019, 4:41 AM Copy code
{
"test": "test"
}Seth Duda
12/19/2019, 4:41 AMbut if you were to return {"test":"<html></html>"}, NS adds in the commented out block in the response.
Seth Duda
12/19/2019, 4:42 AMnot really sure what keywords / patterns trigger it, but html tags do it.
m
michoel
12/19/2019, 4:43 AMInteresting, thanks
s
Seth Duda
12/19/2019, 4:43 AMnp
m
michoel
12/19/2019, 4:45 AMI am also pretty sure they've made changes to this behavior around April this year, looking at my git history that's when I had to adopt this hack on one project that was working perfectly fine until then
s
Seth Duda
12/19/2019, 4:48 AMI ran into this back in Jan and that's when I started setting the Content-Type
Seth Duda
12/19/2019, 4:52 AMIt's an odd feature - I'm guessing there's something sitting in the middle looking for html-ish responses and adding the comment block to the end.
e
ec
12/19/2019, 5:31 AMThanks @Seth Duda for the tip - most likely these offending records contained html tags that were included in the JSON response. I’ll look into setting the Content Type explicitly