You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To ensure consistency and standardization in our data collection process, I suggest creating a new entity specifically dedicated to representing specs. While events represent specific user actions or occurrences, specs define the structure and format of the event data being sent.
So the proposed solution involves introducing separate struct types for different event types, such as PageSpec, TrackSpec, and others, alongside a base BaseSpec struct for common fields across all spec types. This approach will enable developers and users to define and manage specifications for each event type while maintaining a clear and structured schema.
Hello
To ensure consistency and standardization in our data collection process, I suggest creating a new entity specifically dedicated to representing specs. While events represent specific user actions or occurrences, specs define the structure and format of the event data being sent.
please see this link for more information :
specs
So the proposed solution involves introducing separate struct types for different event types, such as PageSpec, TrackSpec, and others, alongside a base BaseSpec struct for common fields across all spec types. This approach will enable developers and users to define and manage specifications for each event type while maintaining a clear and structured schema.
@gohossein
The text was updated successfully, but these errors were encountered: