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(dropdown-menu,context-menu,menubar): set our menu side to default… #581

Merged
merged 1 commit into from
Feb 10, 2025

Conversation

goetzrobin
Copy link
Collaborator

…s if no prev position

we are using some ugly workaround to store the last position, of the menu we opened and then set the side based on that. sometimes there is no last position available so we should just set to defaults and return instead of throwing an error trying to access an undefined object

closes #553

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

Which package are you modifying?

  • accordion
  • alert
  • alert-dialog
  • aspect-ratio
  • avatar
  • badge
  • button
  • calendar
  • card
  • checkbox
  • collapsible
  • combobox
  • command
  • context-menu
  • data-table
  • date-picker
  • dialog
  • dropdown-menu
  • hover-card
  • icon
  • input
  • label
  • menubar
  • navigation-menu
  • pagination
  • popover
  • progress
  • radio-group
  • scroll-area
  • select
  • separator
  • sheet
  • skeleton
  • slider
  • sonner
  • spinner
  • switch
  • table
  • tabs
  • textarea
  • toast
  • toggle
  • tooltip
  • typography

What is the current behavior?

Closes #553

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

…s if no prev position

we are using some ugly workaround to store the last position, of the
menu we opened and then set the side based on that. sometimes
there is no last position available so we should just set to defaults
and return instead of throwing an error trying to access an
undefined object

closes #553
Copy link
Collaborator

@ashley-hunter ashley-hunter left a comment

Choose a reason for hiding this comment

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

Thanks! Great to prevent the error for the time being!

@goetzrobin goetzrobin merged commit eeb722b into main Feb 10, 2025
6 checks passed
@goetzrobin goetzrobin deleted the fix/553 branch February 10, 2025 14:23
elite-benni pushed a commit to elite-benni/spartan that referenced this pull request Feb 12, 2025
…s if no prev position (spartan-ng#581)

we are using some ugly workaround to store the last position, of the
menu we opened and then set the side based on that. sometimes
there is no last position available so we should just set to defaults
and return instead of throwing an error trying to access an
undefined object

closes spartan-ng#553
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.

[BUG] Menu component throws an error when it's triggered
3 participants