Repository navigation
feat(component-library): implement mt-nav component - #1386
Merged
Alastair Fraser (alastair-simon) merged 58 commits intoOct 9, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Alastair Fraser (alastair-simon)
marked this pull request as ready for review
October 5, 2026 16:21
Fabian Hüske (fabianhueske)
requested review from
Arnold Stoba (arnoldstoba) and
Fabian Hüske (fabianhueske)
October 7, 2026 08:05
…d entry-suffix slots
…move the user block to stories
…ns can stay static
Alastair Fraser (alastair-simon)
force-pushed
the
feat/implement-mt-nav-component
branch
from
October 9, 2026 12:07
c36b6a9 to
c9a35b4
Compare
Alastair Fraser (alastair-simon)
dismissed
Fabian Hüske (fabianhueske)’s stale review
October 9, 2026 12:41
changes complete
Arnold Stoba (arnoldstoba)
approved these changes
Oct 9, 2026
@shopware-ag/meteor-admin-sdk
@shopware-ag/meteor-component-library
@shopware-ag/create-meteor-extension
@shopware-ag/meteor-icon-kit
@shopware-ag/meteor-prettier-config
@shopware-ag/stylelint-plugin-meteor
@shopware-ag/meteor-tokens
commit: |
Alastair Fraser (alastair-simon)
deleted the
feat/implement-mt-nav-component
branch
October 9, 2026 15:03
This branch was successfully deployed
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
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.
What
Adds
mt-nav, a sidebar navigation component for Shopware apps.Why
Every Shopware app built its own nav menu, each slightly different. A shared component:
How
Structure
The app passes the menu as data through the
sectionsprop.mt-navis the only public component; it renders two internal parts:mt-nav-section: a group of rows below an optionalheadermt-nav-item: one row, which nests throughchildren(up to three levels)What a row renders depends on its fields:
to: a link throughlinkComponent(router-linkby default)href: a plain anchor, with an external-link icon and a screen reader hint when it opens in a new tabchildrenand noto: a folder button that opens and closes its rowsProps, events and slots
sections: the menu data (NavSection[])linkComponent: the component used fortolinkslabel: accessible name of the landmark, defaults to a translated "Main navigation"isActive: a function that decides which row is the current page, sosectionscan stay static. Settingactiveon a row also works.navigateevent: emitted on link clicks, not on folder togglessuffixslot: rendered after each row label, e.g. for a badge or counterBehaviour
Rows are told apart by an optional
id, falling back to the label.