Skip to content

Enhance navigation item handling with separate IDs for items - #5

Merged
Adammatthiesen merged 1 commit into
mainfrom
fix
Jul 5, 2026
Merged

Enhance navigation item handling with separate IDs for items#5
Adammatthiesen merged 1 commit into
mainfrom
fix

Conversation

@Adammatthiesen

Copy link
Copy Markdown
Member

This pull request refactors the navigation item configuration for the UI and updates how navigation buttons are created and positioned in the PlateMenu. The main focus is to support separate configuration for "previous" and "next" navigation items, and to adjust their placement in the UI layout.

UI Configuration Changes:

  • Added prevNavigationItemId and nextNavigationItemId fields to DisplayItems, replacing the single navigationItemId, to allow different items for previous and next navigation actions.

PlateMenu Logic Updates:

  • Updated the getNavItem method to accept a prev boolean and select the appropriate navigation item ID (prevNavigationItemId or nextNavigationItemId).
  • Modified the creation of navigation buttons to use the new getNavItem signature, passing true for previous and false for next.

UI Layout Adjustments:

  • Changed the slot positions for navigation, back, and clear buttons in the chest template to better align with the new navigation logic and improve UI consistency.

@Adammatthiesen
Adammatthiesen marked this pull request as ready for review July 5, 2026 05:55
@Adammatthiesen
Adammatthiesen merged commit 244d899 into main Jul 5, 2026
1 check passed
@Adammatthiesen
Adammatthiesen deleted the fix branch July 5, 2026 06:01
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