Hi all, As discussed in this PR <https://github.com/apache/incubator-flagon-useralejs/pull/347>, we'd like to ideate on the topic of implementing a schema for the Userale client payloads that are sent to backend servers.
First stab at a problem statement: Userale in its current state does not implement any sort of schema for its payloads. Changes to the payload's shape (as referenced in the PR linked above) can break data pipelines for downstream users. How might we: 1. Validate and version a schema so that downstream users know the shape of data they will receive 2. Maintain the flexible schema management that Userale currently offers Looking forward to the discussion! Best, Gedd Johnson
