Descriptive text is HTML encoded #150
Description
When dealing with freeform text fields like “disabled_facilities” on the product API we get back a blob of text. At the moment I’m assuming this “can” be HTML encoded. As there are other fields like “directions” where the values definitely have HTML in them, Is there any restrictions on any free form text fields or is the above assumption correct?
When integrating at a mobile app level we don’t really “render” in a web browser, not knowing which fields can return different encoded text means we’re currently defaulting to treating them all as potentially having HTML in them. Documenting the fields format would be pretty handy from in integration perspective.