sourcegraph/sourcegraph-public-snapshot

insights: how to represent language stats time scope

Open

#27,151 opened on Nov 5, 2021

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Go (1,374 forks)auto 404
backendcode-insightsdebtgood first issueinsights-settings-migration

Repository metrics

Stars
 (10,290 stars)
PR merge metrics
 (PR metrics pending)

Description

I guess my only concern here is that the semantic of a 0 value interval is ambiguous. What does that mean to a client, and how should one execute the search queries to generate this series based on this information?

I wonder if we just should have a new TimeScope type for a single time point (the most recent for example)? The intention behind the TimeScope was to ultimately have multiple types, some of which would have an interval and others would be different. Maybe this is a justification here? What do you think?

Originally posted by @coury-clark in https://github.com/sourcegraph/sourcegraph/pull/27102#discussion_r743760401

Contributor guide

Research direction
Review the linked PR #27102 and discussion to understand the current TimeScope implementation. Then propose a new TimeScope variant for a single time point, considering how clients would interpret a zero interval value.
Tech stack
go
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50