-
Notifications
You must be signed in to change notification settings - Fork 227
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
Remove hack in synth.py
#642
Comments
synth.py
to replace synth.py
For a super quick fix we could probably just update the regular expression. Better fixes that would allow us to remove the hacks entirely might be:
|
@callmehiphop can you tell me more about the first option (have the gapic-generator create methods)? I'm happy to add any extra code to the codegen templates but I can't understand which code we need to make it not Pub/Sub-specific. |
@alexander-fenster absolutely! I think some sort of getter for the underlying gRPC client would do the trick. To elaborate on why these two methods were stuffed in
|
@JustinBeckwith, any objection to recategorize this as a "type: cleanup", since this doesn't affect users? |
I tried removing the s.replace() hack back on Jan 27 but it looks like it's still broken. I haven't seen fixes for this on the horizon, so I'm going to go ahead and close it out for now. |
I'm happy to move this to another repo (gapic generator maybe?), but we do want to track these kinds of issues with the generators and synth hacks. cc @alexander-fenster |
I'm fine with tracking it, but I've also been tasked with not leaving issues open if we're not fixing them in the particular repo soon. Should I create a new issue in gapic? |
We will try to remove this hack when we move this library to TypeScript generator. |
In that case @alexander-fenster - you ok with just closing this? I figure we'll have a chance to discuss it in the PR that moves us to TS :) |
Sure! (I actually thought it is closed :) ) |
We currently have this hack in
synth.py
:The code that's getting swapped in is creating lint issues in #641. It looks like there is an issue here in the gapic generator causing the pain:
googleapis/gapic-generator#2127
The text was updated successfully, but these errors were encountered: