JuliaIO / JuliaIO/gRPCClient.jl
gRPC.jl monorepo
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 64
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
@tanmaykm I'm getting gRPCServer.jl ready to register and think it would be better to setup a gRPC.jl mono repo to avoid code duplication / simplify testing. I'd like to split things into three packages:
- gRPCCore.jl
- gRPCClient.jl
- gRPCServer.jl
Would something like that be acceptable? We are also not allowed to start without a capital letter for registration anymore, so I'm trying to figure out what to do about that. Renaming gRPCClient -> GRPCClient seems worse than just having an inconsistent naming convention between the package names.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the proposed split into gRPCCore.jl, gRPCClient.jl, and gRPCServer.jl, along with the concern about package names beginning with a capital letter. Check the Julia package registration constraints described in the issue and determine whether the maintainers approve the monorepo structure and naming approach; done means an agreed repository and package plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, julia
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100