From 80d8c667666ffdb6b8e668ef94cc58a93045bd0e Mon Sep 17 00:00:00 2001 From: Sean Perkins Date: Tue, 18 Apr 2023 15:25:44 -0400 Subject: [PATCH] fix(menu): export menu interfaces (#27227) Issue number: N/A --------- ## What is the current behavior? When updating to Stencil v3 ([commit](https://github.com/ionic-team/ionic-framework/commit/1a8bd6d8c6a5227f803250722442199cbfa3510d#diff-83006355bd18aced9f88fd3b27ff6a40527c713b314145c2a34ad54b6361fa87)), we removed many manual exports that are automatically exported by Stencil. This change included removing the `MenuI` type from being exported. This type is not automatically exported since it is not directly associated to a `@Prop`. This causes implementers that previously had a typed value against `MenuI` in v6 for registering menus, to have to import from: ```ts import { MenuI } from "@ionic/core/dist/types/components/menu/menu-interface"; ``` ## What is the new behavior? - Re-exports the `MenuI` interface ## Does this introduce a breaking change? - [ ] Yes - [x] No ## Other information --- core/src/interface.d.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/src/interface.d.ts b/core/src/interface.d.ts index e460d67558..4e2c085a63 100644 --- a/core/src/interface.d.ts +++ b/core/src/interface.d.ts @@ -15,7 +15,7 @@ export { InputCustomEvent } from './components/input/input-interface'; export { CounterFormatter } from './components/item/item-interface'; export { ItemSlidingCustomEvent } from './components/item-sliding/item-sliding-interface'; export { LoadingOptions } from './components/loading/loading-interface'; -export { MenuCustomEvent } from './components/menu/menu-interface'; +export { MenuCustomEvent, MenuI, MenuControllerI } from './components/menu/menu-interface'; export { ModalOptions, ModalCustomEvent } from './components/modal/modal-interface'; export { NavDirection, NavCustomEvent } from './components/nav/nav-interface'; export { PickerOptions, PickerColumnOption } from './components/picker/picker-interface';