fix(menu): export menu interfaces #27227
Merged
Conversation
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
|
|
liamdebeasi
approved these changes
Apr 18, 2023
|
Is |
|
It wouldn't hurt, it is only referenced from |
sean-perkins
changed the title
liamdebeasi
pushed a commit
that referenced
this pull request
Apr 19, 2023
Issue number: N/A --------- <!-- Please refer to our contributing documentation for any questions on submitting a pull request, or let us know here if you need any help: https://ionicframework.com/docs/building/contributing --> <!-- Some docs updates need to be made in the `ionic-docs` repo, in a separate PR. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#modifying-documentation for details. --> <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> When updating to Stencil v3 ([commit](1a8bd6d#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? <!-- Please describe the behavior or changes that are being added by this PR. --> - Re-exports the `MenuI` interface ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->
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.
Issue number: N/A
What is the current behavior?
When updating to Stencil v3 (commit), we removed many manual exports that are automatically exported by Stencil. This change included removing the
MenuItype 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
MenuIin v6 for registering menus, to have to import from:What is the new behavior?
MenuIinterfaceDoes this introduce a breaking change?
Other information