Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: use proto descriptor files as an alternative to plain protos #442

Open
KenxinKun opened this issue Nov 23, 2024 · 0 comments
Open
Assignees

Comments

@KenxinKun
Copy link

A suggestion for v3: allow an alternative input in the form of proto descriptor files (i.e. that the user has already pre compiled with protoc).

Why? It's easy to get proto spec versions out of sync between what's supplied to gripmock and what's use in the codebase.

We use BSR imports into our Golang codebase and it's straightforward to pass in a proto descriptor from the imported package. On the other hand to pass the proto files to gripmock I need to reverse engineer what buf module version my Go package is importing and then use buf export. The chances of mis matching api versions is high.

@rez1dent3 rez1dent3 self-assigned this Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants