Comment by cozzyd
incomplete strings could be fun in certain cases
{"cleanup_cmd":"rm -rf /home/foo/.tmp" }
incomplete strings could be fun in certain cases
{"cleanup_cmd":"rm -rf /home/foo/.tmp" }
I imagine if you reason about incomplete strings as a sort of “unparsed data” where you might store or transport or render it raw (like a string version of printing response.data instead of response.json()), but not act on it (compare, concat, etc), it’s a reasonably safe model?
I’m imagining it in my mental model as being typed “unknown”. Anything that prevents accidental use as if it were a whole string… I imagine a more complex type with an “isComplete” flag of sorts would be more powerful but a bit of a blunderbuss.
If any part of that value actually made it, unchecked, to execution, then you have bigger problems than partial JSON keys/values.