Unify the syntax for property values in reconciliation queries and data extension responses

reconciliation-api / specs

Specifications of the reconciliation API

https://reconciliation-api.github.io/specs/draft/

31 stars 9 forks source link

Unify the syntax for property values in reconciliation queries and data extension responses #94

Open wetneb opened 2 years ago

wetneb commented 2 years ago

The way we serialize our property values in JSON is different depending on the context: see the JSON schemas for reconciliation queries and for data extension responses.

It would be nice to unify this.

wetneb commented 1 year ago

Moreover, there is currently an inconsistency in the specs (links are to the 0.2 specs, but we have the same problems in the current draft):

the Property values section declares that properties are one of the following:
- A string;
- A boolean;
- An integer;
- A floating-point value;
- An entity.
the schemas for the data extension response do not include an option for booleans, and include an option for null values and dates, which are not mentioned above.