http-extensions
http-extensions copied to clipboard
Algorithms for retrofit compatibility fixes
We have the following text,
for parameters and dictionary keys:
compatibility can be improved by force-lowercasing them when parsing
for parameter delimiters:
Compatibility can be improved by allowing such whitespace when parsing
and for strings:
Compatibility can be improved by unescaping other characters before parsing
It would be very helpful if this could be expressed as an algorithm, or as modifications to the existing SF algorithms. I say this because while you might be able to make the change for strings across an entire field value, I don't think that it is generally safe to downcase an entire field value and expect it to work.
That suggests targeted changes to the SF algorithms for compatibility with retrofit fields. In that case, you probably don't want those compatibility changes affecting how native SF definitions are processed. Being more precise about the processing rules here might head off problems of overly broad application.