-
Notifications
You must be signed in to change notification settings - Fork 80
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: integer fields are displayed as floats when using describe with -o=yaml #650
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jooola
requested changes
Dec 19, 2023
jooola
changed the title
fix: integer fields are displayed as floats when using describe with -o=yaml
fix: integer fields are displayed as floats when using described with -o=yaml
Dec 19, 2023
jooola
changed the title
fix: integer fields are displayed as floats when using described with -o=yaml
fix: integer fields are displayed as floats when using describe with -o=yaml
Dec 19, 2023
jooola
approved these changes
Dec 19, 2023
phm07
added a commit
that referenced
this pull request
Dec 20, 2023
…yaml (#651) Continuation #650, closes #638 When outputting a resource after creation, it is first converted into a schema struct. This fixes bugs like #638 and also makes all schema outputs (describe, list, create) consistent. --------- Co-authored-by: jo <[email protected]>
jooola
pushed a commit
that referenced
this pull request
Dec 21, 2023
🤖 I have created a release *beep* *boop* --- ## [1.41.1](v1.41.0...v1.41.1) (2023-12-21) ### Bug Fixes * allow multiple --type flags for metrics commands ([#649](#649)) ([69346f7](69346f7)), closes [#642](#642) * integer fields are displayed as floats when using create with o=yaml ([#651](#651)) ([2d42fcd](2d42fcd)) * integer fields are displayed as floats when using describe with -o=yaml ([#650](#650)) ([ee4c51e](ee4c51e)), closes [#638](#638) * wording when metrics are not yet available ([#639](#639)) ([9298c46](9298c46)) --- 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #638