feat: migrate billing products and features APIs to Connect RPC #1172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Migrate billing products and features APIs from gRPC to Connect RPC format as part of the billing system modernization.
Progress: 8/8 APIs Complete (100%) ✅
✅ Completed APIs:
Migration Complete! 🎉
All billing products and features APIs have been successfully migrated from gRPC to Connect RPC format. The migration maintains 100% backward compatibility while modernizing the API interface.
Key Changes Made:
Technical Implementation:
request.GetField()torequest.Msg.GetField()connect.NewResponse(&ResponseType{...})connect.NewError(code, error)formatTest Coverage:
Each migrated API includes comprehensive test coverage with:
All APIs maintain identical business logic while adopting Connect RPC interface patterns. The migration provides a solid foundation for modern API development with improved type safety and better tooling support.