DEVDOCS-5996: [Update] channel ID is no longer a requirement for toke…#364
Merged
bc-traciporter merged 7 commits intomainfrom Jul 11, 2024
Merged
DEVDOCS-5996: [Update] channel ID is no longer a requirement for toke…#364bc-traciporter merged 7 commits intomainfrom
bc-traciporter merged 7 commits intomainfrom
Conversation
bc-traciporter
added
the
ready for review
bc-rafsierk
reviewed
Jul 9, 2024
bc-rafsierk
reviewed
Jul 10, 2024
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
bc-rafsierk
previously approved these changes
Jul 10, 2024
bc-tgomez
approved these changes
Jul 11, 2024
becomevocal
pushed a commit
that referenced
this pull request
Aug 10, 2024
#364) …n creation <!-- Ticket number or summary of work --> # [DEVDOCS-5996] ## What changed? * removed text regarding the requirement to enter a channel ID when creating a Storefront token * Fixed incorrect example * Created a ticket to remove duplicated request fields. ## Release notes draft We're happy to announce that you can use a channel ID or channel IDs when creating a Storefront token. (needs review) <!-- 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]. --> * ## Anything else? <!-- Add related PRs, salient notes, additional ticket numbers, etc. --> ping {names} [DEVDOCS-5996]: https://bigcommercecloud.atlassian.net/browse/DEVDOCS-5996?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
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
3 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.
…n creation
DEVDOCS-5996
What changed?
Release notes draft
We're happy to announce that you can use a channel ID or channel IDs when creating a Storefront token. (needs review)
Anything else?
ping {names}