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.

Sign up for GitHub

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

Jump to bottom

ParseErrors for unknown enum responses for GAPICs over REST #992

Open
busunkim96 opened this issue Sep 14, 2021 · 2 comments
Open

ParseErrors for unknown enum responses for GAPICs over REST #992

busunkim96 opened this issue Sep 14, 2021 · 2 comments
Assignees
@vchudnov-g @busunkim96
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@busunkim96
Copy link
Contributor

When a REST endpoint adds a new enum to a response, older versions of the GAPIC library without the enum definition raise parse errors.

Details and status in this document.

See googleapis/python-compute#111
@busunkim96 busunkim96 added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Sep 14, 2021
@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed 🚨 This issue needs some love. labels Dec 13, 2021
@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label Mar 13, 2022
@vchudnov-g
Copy link
Contributor

We are working on server-side support for solving this. See internal docs.

@vchudnov-g vchudnov-g removed the 🚨 This issue needs some love. label Mar 15, 2022
@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label Mar 15, 2022
@parthea parthea added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. and removed type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. 🚨 This issue needs some love. labels Apr 30, 2022
@parthea
Copy link
Contributor

parthea commented Apr 30, 2022

Converting to feature request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vchudnov-g vchudnov-g

@busunkim96 busunkim96

Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@parthea @vchudnov-g @busunkim96 @yoshi-automation