-
Notifications
You must be signed in to change notification settings - Fork 0
Add stream type constant stability tests #8
Copy link
Copy link
Open
Labels
area/transportBobravoz gRPC transport changes.Bobravoz gRPC transport changes.good first issueSmall, well-scoped tasks for new contributors.Small, well-scoped tasks for new contributors.help wantedLooking for community contributions.Looking for community contributions.kind/testsTesting, CI, or verification-only changes.Testing, CI, or verification-only changes.priority/lowNice-to-have or backlog item.Nice-to-have or backlog item.
Metadata
Metadata
Assignees
Labels
area/transportBobravoz gRPC transport changes.Bobravoz gRPC transport changes.good first issueSmall, well-scoped tasks for new contributors.Small, well-scoped tasks for new contributors.help wantedLooking for community contributions.Looking for community contributions.kind/testsTesting, CI, or verification-only changes.Testing, CI, or verification-only changes.priority/lowNice-to-have or backlog item.Nice-to-have or backlog item.
Problem statement
transport/stream_types.godefines 16 stream type string constants used across the ecosystem. This file has zero test coverage. While constants themselves can't have bugs, accidental value changes would silently break all consumers.Proposed change
Add
transport/stream_types_test.gowith a contract stability test:This acts as a regression guard — any accidental rename or value change will fail CI.
Affected area
Compatibility / migration
Test-only. No behavior change.
Additional context
These constants are consumed by bubu-sdk-go, bobravoz-grpc, and potentially future Python/TypeScript SDKs. A value change without coordination would silently break packet routing. Identified during QA review.