Skip to content

Move saved-search-editor up to parent component #1487

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

Merged

Conversation

DanielRyanSmith
Copy link
Collaborator

@DanielRyanSmith DanielRyanSmith commented May 13, 2025

This change fixes some known stacking issues which caused some elements to render above the saved search dialog. The webstatus-saved-search-editor component now lives in the webstatus-overview-content component, which alleviates stacking issues.

A new event, open-saved-search-editor, is dispatched in webstatus-saved-search-controls, and handled in webstatus-overview-content, to trigger the open action of the saved search dialog.

All tests have been moved and adjusted, the the overall number not being changed.

@jcscottiii
Copy link
Collaborator

Thanks for tackling this. One thing to note:

A new function, openSavedSearchDialog(), is now passed down

If the interaction happens in a sub component and needs to let an ancestor component know, it should raise an event. [1]

@DanielRyanSmith
Copy link
Collaborator Author

If the interaction happens in a sub component and needs to let an ancestor component know, it should raise an event. [1]

I see - I'll update the implementation to use this paradigm. 🙂

@DanielRyanSmith DanielRyanSmith marked this pull request as ready for review May 15, 2025 22:06
Copy link
Collaborator

@jcscottiii jcscottiii left a comment

Choose a reason for hiding this comment

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

LGTM with one suggestion/question.

@jcscottiii jcscottiii added this pull request to the merge queue May 16, 2025
Merged via the queue into GoogleChrome:main with commit 7d9d4b2 May 16, 2025
3 checks passed
@jcscottiii jcscottiii mentioned this pull request May 16, 2025
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.

2 participants