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(headless, atomic): ensure components are enabled/disabled correctly when an invalid tab id is provided #4944

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

fpbrault
Copy link
Contributor

@fpbrault fpbrault commented Feb 6, 2025

This PR ensures that when providing an invalid tab value, the active tab correctly falls back to the first available tab, with the tab-specific components enabled/disabled based on which tab is active.

https://coveord.atlassian.net/browse/KIT-3945

Copy link

github-actions bot commented Feb 6, 2025

Pull Request Report

PR Title

❌ Title should follow the conventional commit spec:
<type>(optional scope): <description>

Example: feat(headless): add result-list controller

Live demo links

Bundle Size

File Old (kb) New (kb) Change (%)
case-assist 244.2 244.2 0
commerce 355.5 355.5 0
search 415.5 415.5 0
insight 406.7 406.9 0.1
recommendation 256.3 256.4 0
ssr 409.3 409.3 0
ssr-commerce 373.2 373.2 0

@@ -98,3 +101,8 @@ export const restoreSearchParameters = createAction(
(payload: SearchParameters) =>
Copy link
Contributor

Choose a reason for hiding this comment

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

Since tabs are now restored through a distinct action, should we mark the tab property in the SearchParameters interface as deprecated, or maybe even remove it altogether?

@@ -98,3 +101,8 @@ export const restoreSearchParameters = createAction(
(payload: SearchParameters) =>
validatePayload(payload, searchParametersDefinition)
);

export const restoreTab = createAction(
Copy link
Contributor

Choose a reason for hiding this comment

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

The new action should be exposed in the public interface through the search-parameters-actions-loader

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.

3 participants