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

fix(snippetgen): remove special handling for resource paths #1134

Merged
merged 5 commits into from
Jan 28, 2022

Conversation

busunkim96
Copy link
Contributor

There are some bugs in this implementation that stop generation
in some APIs and result in incorrect snippets getting generated
for others. Back out this feature for now so we can move forward
with enabling snippetgen for all APIs.

There are some bugs in this implementation that stop generation
in some APIs and result in incorrect snippets getting generated
for others. Back out this feature for now so it can be re-added
later.
@software-dov
Copy link
Contributor

software-dov commented Jan 19, 2022

Which APIs are causing problems? If we can determine what the common factors are we could yank them into a test.

@busunkim96
Copy link
Contributor Author

Which APIs are causing problems? If we can determine what the common factors are we could yank them into a test.

Good idea, I'll open an issue that properly describes the issue. The current implementation can't handle fields that represent resources and are nested more than one level deep. This doesn't happen in any of the current golden APIs. IIRC I think it appeared in some AI/ML APIs with a bigger surface that define more resources.

I made some progress towards fixing it in November, but am now having trouble figuring out what I had left to do 😅 . The snippetgen priorities for this quarter are (1) getting snippets into the docstrings and (2) generating metadata, so I decided to back this out to land the higher priority items first.

@busunkim96
Copy link
Contributor Author

I've opened an issue to track re-adding f-strings for resource paths #1144. Pub/Sub runs into the bug that halts generation and should be a good candidate for tests when I'm ready to work on this in the future.

@busunkim96 busunkim96 marked this pull request as ready for review January 20, 2022 22:41
@busunkim96 busunkim96 requested review from a team as code owners January 20, 2022 22:41
@busunkim96
Copy link
Contributor Author

@software-dov Friendly ping

@busunkim96 busunkim96 added the automerge Merge the pull request once unit tests and other checks pass. label Jan 28, 2022
@gcf-merge-on-green gcf-merge-on-green bot merged commit 4ea2d11 into main Jan 28, 2022
@gcf-merge-on-green gcf-merge-on-green bot deleted the remove-resource-path- branch January 28, 2022 17:12
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Jan 28, 2022
gcf-merge-on-green bot pushed a commit that referenced this pull request Jan 28, 2022
I accidentally merged #1134 without updating the golden files for snippetgen. This PR updates the golden files and marks the 'snippetgen' check required.
gcf-merge-on-green bot pushed a commit that referenced this pull request Jan 28, 2022
🤖 I have created a release *beep* *boop*
---


## [0.62.0](v0.61.0...v0.62.0) (2022-01-28)


### Features

* adds REST server-streaming support. ([#1120](#1120)) ([812cf3e](812cf3e))
* expose extended operations annotations within generator ([#1145](#1145)) ([e7bee70](e7bee70))


### Bug Fixes

* add special method parameters to set of reserved module names ([#1168](#1168)) ([8078961](8078961))
* fix snippetgen golden file ([#1170](#1170)) ([13b2028](13b2028))
* **snippetgen:** remove special handling for resource paths ([#1134](#1134)) ([4ea2d11](4ea2d11))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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

Successfully merging this pull request may close these issues.

2 participants