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

With REST only clients map fields are having trouble parsing the correct resourceType #544

Open
dwsupplee opened this issue Dec 5, 2022 · 0 comments
Open

With REST only clients map fields are having trouble parsing the correct resourceType #544

dwsupplee opened this issue Dec 5, 2022 · 0 comments
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@dwsupplee
Copy link
Contributor

For reference: #540 (comment)

This primarily came up with the compute paginated snippets. When grabbing the resourceType it was coming back as a class of "ItemsEntry", despite the protos indicating something else. We should research why this is happening and solve for it so we can re-enable the inline var block.
@dwsupplee dwsupplee 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 Dec 5, 2022
@dwsupplee dwsupplee mentioned this issue Dec 5, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dwsupplee