protocolbuffers/protobuf

inconsistent handling of keywords and conflicts

Open

#10,491 opened on Sep 1, 2022

View on GitHub
 (1 comment) (3 reactions) (0 assignees)C++ (16,128 forks)batch import
help wantedprotoc

Repository metrics

Stars
 (71,223 stars)
PR merge metrics
 (Avg merge 2d 11h) (185 merged PRs in 30d)

Description

Various code generators and languages have interesting non-overlapping sets of keywords. Protobuf as a whole does not handle these things consistently (sometimes it mangles them, sometimes it generates code that doesn't compiler). When the mangling causing conflicts with other feels we are one again inconsistent. Then we are sad.

What needs to happen is a systematic push to

  1. figure out what we do now
  2. propose a unified solution
  3. move things to it

Contributor guide

Research direction
Map out current keyword handling in all protobuf code generators and languages, identify inconsistencies and conflicts, then propose a unified mangling or resolution scheme.
Tech stack
None
Domain
backendapitoolingdeveloper experience
Issue type
Refactor
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.
1-2 days
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.
Needs investigation
Prerequisites
protobufcode generation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30