Getting/setting attribute values as text

[fgalan]

Getting an attribute value encoded as text:

• Operation: GET /v2/entities//attrs//value
• Text is returned when text/plain is in Accept with more priority than application/json (check Accept header rules in the HTTP specification) or "options=text" is used (overriding the Accept header).
• Attribute values using number or booleans as native JSON type are translated to text at rendering time.

Setting an attribute value encoded as text:

• Operation: PUT /v2/entities//attrs//value
• The payload is considered as text if Content-Type is text/plain
• The serviceRoutine dealing with this should apply a heuristic, so if the text is a valid number it will be passed as number to mongoBackend (the same will apply in the future for dates Using special type "date", should be converted to ISODate() in mongo? #1107, once it is implemented).

Related with (more broad): #1001

[fgalan]

If the value attribute is a compound value, getting such attribute value as text will return an "string-fication" of the JSON.

[fgalan]

PR #1182 completed the "getting" par of the issue.

Regarding the "setting" part, it is better to defer to 0.26.0, as currently is being discussed the final behaviour of such operation.

[fgalan]

Actually, this was part of #1259. Thus, closing.