Escaping Input - Expectation of the API


#1

This is a question for the fellow users of the APIs, and in particular anyone using the ROADS API.

Currently when POSTing an encoded polyline to the ROADS API, it is an unspecified requirement to escape any backslashes so that the json remains properly formatted. The other option would be for the API itself to ALLOW_BACKSLASH_ESCAPING_ANY_CHARACTER so that the encoded polyline could be sent directly.

I can see arguments for each case, however I am leaning on the side that expecting developers to escape backslashes, and maintain json format is the right way to do things. It is also possible that many libraries currently in use may automagically escape the backslashes and it will be extra effort for the developer to override this functionality.

What is the consensus here?