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

[Web] Fix error when using sidenav search while on non-sidenav section #47772

Merged
merged 1 commit into from
Oct 21, 2024

Conversation

rudream
Copy link
Contributor

@rudream rudream commented Oct 21, 2024

This PR fixes a bug in the search which didn't handle currentView being undefined, which occurs when the user is on a page which isn't part of the sidenav (such as Account Settings). currentView is intended to represent the current sidenav section that the user is on, this is used to highlight that section in the sidenav to indicate it as being active. This meant that using the sidenav search while on one of those pages would trigger an error, since it would be a page not on the sidenav and thus currentView would be undefined.

@rudream rudream added the no-changelog Indicates that a PR does not require a changelog entry label Oct 21, 2024
@github-actions github-actions bot requested review from gzdunek and ravicious October 21, 2024 19:58
@rudream rudream enabled auto-merge October 21, 2024 20:06
@rudream rudream added this pull request to the merge queue Oct 21, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 21, 2024
@rudream rudream added this pull request to the merge queue Oct 21, 2024
Merged via the queue into master with commit eef6f75 Oct 21, 2024
41 of 43 checks passed
@rudream rudream deleted the yassine/fix-search-error branch October 21, 2024 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-changelog Indicates that a PR does not require a changelog entry size/sm ui
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants