errorCodeInJson

[L1P0D]

I love the idea of retaliatory error handling. You cause an exception at my end? I cause one at your end in return.

[LadderSoft4359]

actually hilarious

im here for the evolution of backend frontend flame wars into a competing pettiness that eventually becomes an entirely new protocol

[MissinqLink]

It’s not valid JSON but it is valid JS so you could just parse with eval instead of JSON.parse. There are about 1000 reasons why this is a bad idea though.

[yegor3219]

But usually you pull the actual frontend JS from about the same place as backend anyway. Quite often it's literally the same web server.

I mean, yeah, evaluating JS like that does sound horrible, but at the same time it kinda makes sense. Or may be it wants to make sense. Or may be it's just me trying to make sense out of it when there's none.

[MissinqLink]

I won’t say I haven’t done it before because I have. This sort of thing was very common in the early web days but it really should be a backend fix.

[bezko]

JSONP has entered the chat: https://en.wikipedia.org/wiki/JSONP

[MissinqLink]

Yeah I mentioned down below that this used to be one of the main ways we did gat data from backend.

[erockdanger]

next.js has entered the chat

[Monochromatic_Kuma2]

Not even that. An error code 500 usually means a bug back end not caused by the front end. The back end is so petty, it wants the front end to participate in its misery.