Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wetneb opened this issue Jul 27, 2022 · 1 comment

Comments

@wetneb
Copy link
Member

wetneb commented Jul 27, 2022

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
Copy link
Member Author

wetneb commented Oct 8, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant