Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(menu): remove main attribute that was supposed to removed in v5 #24565

Merged
merged 3 commits into from
Jan 12, 2022

Conversation

liamdebeasi
Copy link
Contributor

Pull request checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • Build (npm run build) was run locally and any changes were pushed
  • Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

What is the current behavior?

Issue Number: resolves #24563
The main attribute was removed in Ionic 5 but did not actually get removed in Ionic 5 despite being noted in the breaking changes: https://github.com/ionic-team/ionic-framework/blob/main/BREAKING.md#menu

What is the new behavior?

  • Removed the menu attribute support for real this time.
  • I also updated some of the checks below since the linter pointed out that they were not allowed.

Does this introduce a breaking change?

  • Yes
  • No (Technically a change in behavior, but support for this was officially dropped in Ionic 5, so developers should not have been using it anyway)

Other information

@liamdebeasi liamdebeasi requested a review from a team as a code owner January 12, 2022 15:21
@github-actions github-actions bot added the package: core @ionic/core package label Jan 12, 2022
const content = this.contentId !== undefined
? document.getElementById(this.contentId)
: parent && parent.querySelector && parent.querySelector('[main]');
: null;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opted for null because getElementById returns null is no element was found.


if (!content || !content.tagName) {
// requires content element
if (content === null) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If content is defined as an element, then tagName is defined: https://developer.mozilla.org/en-US/docs/Web/API/Element/tagName. Nothing on MDN indicates tagName could be the empty string (which is falsy in this case)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
package: core @ionic/core package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug: Karma incorrectly reports [main] attribute deprecation
2 participants