Skip to content

[UPMERGE] 5.1 -> 2026.x - #3126

Open
github-actions[bot] wants to merge 3 commits into
2026.xfrom
upmerge/5.1_2026.x
Open

[UPMERGE] 5.1 -> 2026.x#3126
github-actions[bot] wants to merge 3 commits into
2026.xfrom
upmerge/5.1_2026.x

Conversation

@github-actions

Copy link
Copy Markdown

This PR has been generated automatically.

Remember! The upmerge should always be merged with using Merge pull request button.

In case of conflicts, please resolve them manually with usign the following commands:

git fetch upstream
gh pr checkout <this-pr-number>
git merge upstream/2026.x -m "Resolve conflicts between 5.1 and 2026.x"

dpfaffenbauer and others added 3 commits July 27, 2026 14:54
The entity list, the index class-definition/selected-fields trees and the variant
generator each rendered a hand-rolled antd Tree with their own .ant-tree-* overrides,
so they looked nothing like Pimcore's trees. They now use TreeElement from
@pimcore/studio-ui-bundle, which carries the Pimcore node paddings, hover/selected
colors, chevron switcher and icon slot.

Titles are plain strings (counts and type hints go into the string, the way Pimcore
does it) and context menu entries are declared as node actions. titleRender is only
used where a wrapper element is unavoidable: drag-and-drop and double-click. Those
wrappers render a block-level div inside .ant-tree-title, which is why the nodes carry
'ant-tree-node--has-drag-and-drop' plus a single height rule — the same fix Pimcore
applies to its own drag wrappers.

Also share antd, antd-style and their peers as module federation singletons. Without
that every CoreShop remote instantiated its own antd and rendered outside Pimcore's
ConfigProvider/antd-style theme, falling back to antd's default tokens (blue instead
of the Pimcore palette).

Adds `npm run clean:builds` to drop generated Studio build output locally.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
[Studio] Render CoreShop trees with Pimcore's TreeElement
@sonarqubecloud

Copy link
Copy Markdown

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