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)!: default value of originLevel3 updated to be a valid value #4426

Closed
wants to merge 6 commits into from

Conversation

mmitiche
Copy link
Contributor

SFINT-5663

The previous default value of the originLevel3 was the following: default, this value is considered invalid as it is an invalid URL, the DataHealth dashboard is showing the following message on analytics events where this invalid value was used:

Screenshot 2024-08-12 at 1 00 21 PM

In this PR i'm updating this default value by making it an empty string which is considered a valid value for OriginLevel3.

@mmitiche mmitiche added this to the V3 milestone Sep 17, 2024
@mmitiche mmitiche requested a review from a team as a code owner September 17, 2024 19:24
Copy link

github-actions bot commented Sep 17, 2024

Pull Request Report

PR Title

✅ Title follows the conventional commit spec.

Live demo links

Bundle Size

File Old (kb) New (kb) Change (%)
case-assist 239.2 239.2 0
commerce 337.8 337.8 0
search 407.2 407.2 0
insight 392.1 392.1 0
recommendation 250 250 0
ssr 401.3 401.3 0
ssr-commerce 350 350 0

SSR Progress

Use case SSR (#) CSR (#) Progress (%)
search 39 44 89
recommendation 0 4 0
case-assist 0 6 0
insight 0 27 0
commerce 0 15 0
Detailed logs search : buildInteractiveResult
search : buildInteractiveInstantResult
search : buildInteractiveRecentResult
search : buildInteractiveCitation
search : buildGeneratedAnswer
recommendation : missing SSR support
case-assist : missing SSR support
insight : missing SSR support
commerce : missing SSR support

@louis-bompart
Copy link
Collaborator

image
After discussing this issue with @mmitiche, we agree that there is a need to reassess it, as it may require backend changes.

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