Skip to content

ISSUE-57: [update] Catalog Category Tree Categories, change id to category_id#58

Merged
slsriehl merged 1 commit intomainfrom
ISSUE-57
Jan 25, 2024
Merged

ISSUE-57: [update] Catalog Category Tree Categories, change id to category_id#58
slsriehl merged 1 commit intomainfrom
ISSUE-57

Conversation

@slsriehl
Copy link
Contributor

@slsriehl slsriehl commented Jan 25, 2024

ISSUE-57

What changed?

  • change id to category_id where appropriate

Release notes draft

  • We fixed a bug in the Category Trees spec that incorrectly described a category response object as containing ids, rather than category_ids. Thanks to @atensoftware for raising this in Issue 57!

Anything else?

ping {names}

@slsriehl slsriehl self-assigned this Jan 25, 2024
@slsriehl slsriehl merged commit 41cf4c3 into main Jan 25, 2024
@slsriehl slsriehl deleted the ISSUE-57 branch January 25, 2024 17:40
bc-tgomez pushed a commit that referenced this pull request Apr 26, 2024
…egory_id (#58)

<!-- Ticket number or summary of work -->
# ISSUE-57
* #57


## What changed?
<!-- Provide a bulleted list in the present tense -->
* change id to category_id where appropriate

## Release notes draft
<!-- Provide an entry for the release notes using simple, conversational
language. Don't be too technical. Explain how the change will benefit
the merchant and link to the feature.

Examples:
* The newly-released [X feature] is now available to use. Now, you’ll be
able to [perform Y action].
* We're happy to announce [X feature], which can help you [perform Y
action].
* [X feature] helps you to create [Y response] using the [Z query
parameter]. Now, you can deliver [ex, localized shopping experiences for
your customers].
* Fixed a bug in the [X endpoint]. Now the [Y field] will appear when
you click [Z option]. -->
* We fixed a bug in the Category Trees spec that incorrectly described a
category response object as containing `id`s, rather than
`category_id`s. Thanks to @atensoftware for raising this in Issue 57!

## Anything else?
<!-- Add related PRs, salient notes, additional ticket numbers, etc. -->

ping {names}
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.

1 participant