trends

type Interval string

type Measure string

type MeasurePoint struct {
	Date  time.Time `json:"date"`
	Value float64   `json:"value"`
	N     int       `json:"n"`
}

type MeasureResult struct {
	Event    string         `json:"event"`
	Property string         `json:"property"`
	Measure  Measure        `json:"measure"`
	Points   []MeasurePoint `json:"points"`
	Total    float64        `json:"total"`
	N        int            `json:"n"` // total events that carried a numeric value
	// Truncated: same meaning as Result.Truncated — the span cap trimmed the oldest buckets,
	// so Points cover less of the window than Total/N do. Total stays the honest window
	// aggregate (sum=1005) even when the rendered bars only add to 5; without this flag that
	// 200x gap looked like the response contradicting itself for no stated reason.
	Truncated bool `json:"truncated,omitempty"`
}

type MeasureSeries struct {
	Value string  `json:"value"`
	Total float64 `json:"total"`
	N     int     `json:"n"`
}

type Point struct {
	Date  time.Time `json:"date"`
	Count int       `json:"count"`
}

type Result struct {
	Event  string  `json:"event"`
	Unique bool    `json:"unique"` // true = distinct users, false = raw count
	Points []Point `json:"points"`
	Total  int     `json:"total"`
	// Truncated marks that the display cap (maxDayBuckets / the hourly 744) trimmed the OLDEST
	// buckets: Points cover less than the requested window, Total still covers all of it. It is
	// set rather than left implicit because a reader can otherwise only conclude that the number
	// and the chart disagree — which is the same thing as not trusting either.
	Truncated bool `json:"truncated,omitempty"`
}

type Series struct {
	Value  string  `json:"value"`
	Points []Point `json:"points"`
	Total  int     `json:"total"`
}