envoyproxy/envoy

Improve v2->v3 tooling for detecting unused Protobuf messages

Open

#8,839 opened on Oct 31, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
api/v3help wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Full discussion in PR #8776. TL;DR the tooling removes deprecated protobuf fields, but if the deprecated field was a unique message type that was only used by deprecated fields, the tooling still leaves that now-unused type around.

Contributor guide

Research direction
Inspect the tooling scripts in the repository related to v2 >v3 Protobuf migration, specifically the logic that removes unused types after deprecated field removal.
Tech stack
cpp
Domain
backendtooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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
GitC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60