-
Notifications
You must be signed in to change notification settings - Fork 17
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
Rename packages #219
Rename packages #219
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we're missing a couple of bits, see comments below. Should the extension for generated files remain _connectquery.ts
?
@@ -1,5 +1,5 @@ | |||
{ | |||
"name": "@connectrpc/protoc-gen-connect-query", | |||
"name": "@connectrpc/protoc-gen-connect-react-query", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we rename the npm binary as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah right, yeah, good catch.
Co-authored-by: Timo Stamm <[email protected]>
That's a good question. I think it stands to reason that it should be |
@timostamm how do you feel about using |
Closing this until we can discuss what renaming would cost us, regarding users migrating to new packages. |
Renaming
connect-query
toconnect-react-query
andprotoc-gen-connect-query
toprotoc-gen-connect-react-query
. This makes it clear that these packages still very much depend on running in a react environment.These changes will be published as v1