feat[plugins][commerceLayer]: ENG-11943 Display SKU/Bundle Code Instead of ID in Commerce Layer Plugin#4505
Merged
AishwaryaParab merged 1 commit intomainfrom Apr 7, 2026
Conversation
AishwaryaParab
requested review from
a team and
anaghav2023
and removed request for
a team
|
|
View your CI Pipeline Execution ↗ for commit 88e1e32
☁️ Nx Cloud last updated this comment at |
midhunadarvin
approved these changes
Apr 7, 2026
AishwaryaParab
added a commit
that referenced
this pull request
Apr 7, 2026
…in-tools and commercelayer plugins (#4506) ## Description Bumping up the versions for plugin-tools and commercelayer plugins. Related PR (merged): #4505 _Screenshot_ N/A <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Low risk version/lockfile bumps only; main risk is publishing/consuming the new `@builder.io/plugin-tools@0.0.9` package in `plugin-commercelayer` without runtime code changes. > > **Overview** > Bumps `@builder.io/plugin-tools` from `0.0.8` to `0.0.9` (package + lockfile). > > Bumps `@builder.io/plugin-commercelayer` from `0.1.4` to `0.1.5` and updates its dependency/lockfile to consume `@builder.io/plugin-tools@0.0.9` (including updated tarball integrity metadata). > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 0bf5f74. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
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
2 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.
Description
When a SKU or Bundle is selected in the Commerce Layer plugin, the field label displays the internal Commerce Layer ID (e.g., nPwySKzvQM) instead of the human-readable SKU/Bundle code (e.g., 833600101). This makes it difficult for editors to identify which SKU or Bundle is selected at a glance.
The
ResourcePreviewCellcomponent inplugin-toolswas usingresource.id(the internal ID) for the label. We're now usingresource.handleto display the SKU Code.Screenshot
SKU created in Commerce Layer:
BEFORE:
AFTER:
Note
Low Risk
Low risk UI-only change that affects how selected resources are labeled in the picker/preview, with a safe fallback to
idwhenhandleis missing.Overview
Updates
ResourcePreviewCellinResourcesPicker.tsxto display a resource’s human-friendlyhandle(e.g., SKU/bundle code) alongside the title instead of the internalid, falling back toidwhen nohandleis available.Reviewed by Cursor Bugbot for commit 88e1e32. Bugbot is set up for automated code reviews on this repo. Configure here.