fix(Global Catalog): fix price field capitalization#265
Merged
Conversation
Signed-off-by: Ben Buchanan <buchanan@ibm.com>
|
|
padamstx
changed the title
padamstx
reviewed
Mar 13, 2025
Contributor
padamstx
left a comment
padamstx
left a comment
There was a problem hiding this comment.
LGTM, just had a question about the removal of the example code fragment for the getPricing() operation.
Signed-off-by: Ben Buchanan <buchanan@ibm.com>
ibm-devx-sdk
pushed a commit
that referenced
this pull request
Mar 13, 2025
## [0.61.1](0.61.0...0.61.1) (2025-03-13) ### Bug Fixes * **Global Catalog:** fix price field capitalization ([#265](#265)) ([6cfe485](6cfe485))
Contributor
|
🎉 This PR is included in version 0.61.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
PR summary
Regen after api definition fixes like Price to price, include url field for object update, and support deployment_region query param
PR Checklist
Please make sure that your PR fulfills the following requirements:
Current vs new behavior
Fixes object update and price field syntax
Does this PR introduce a breaking change?
Other information
Integration tests
Example tests