-
Notifications
You must be signed in to change notification settings - Fork 349
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
feat: add a no-tags option to the type-registry #688
base: main
Are you sure you want to change the base?
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 other than the *.bin
issue this PR lgtm! Let me know if running yarn proto2bin
with dockers gets them fixed up. If not, we can either figure out how to get the M1 docker output consistent, or I can just revert the *.bin changes directly on this branch/something like that.
@@ -688,15 +692,15 @@ export function responseType( | |||
methodDesc: MethodDescriptorProto, | |||
typeOptions: { keepValueType?: boolean; repeated?: boolean } = {} |
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.
Looks like the typeOptions
param is not used anymore? Lets just drop it if so?
} | ||
// if (options.useDate && rawOutputType.toString().includes("Timestamp")) { | ||
// decode = code`data => ${utils.fromTimestamp}(${rawOutputType}.decode(new ${Reader}(data)))`; | ||
// } |
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 assume this is related to #689 , just checking that you wanted to include commenting out this code in this PR?
The $types are getting in the way of usability of the code we're writing, but the registry itself is useful.