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
LPS-123084 Calculate the segments only when there are experiences associated with the layout. #686
Conversation
…setCategoryParameters
… it in the generated tests
…ng user permissions as stated by LPS-5695/LPE-1585
…can only be changed at instance settings so site/organization roles does not need to be considered
…L which doesn't run the JS
…to retrieve the relevant MBDiscussion entry.
…rk well with fields within fieldset
…es just like we do for non-repeatable fields
Javascript doesnt have a proper integer type, it uses a floating point representation for all numbers. This may lead to weird rounding errors when storing longs/integers as raw numbers in a JSON object.
✔️ ci:test:sf - 1 out of 1 jobs passed in 3 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-123084.4 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#4877 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#7471 |
ci:forward |
CI is automatically triggering the following test suites:
The pull request will automatically be forwarded to the user
|
Skipping previously passed test suites: |
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#96987 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#7123 |
Motivation
The main goal of this pull is to calculate SegmentsExperienceIds only when the layout has an associated experience.
This is the fourth pull to merge into master the Performance Issue fix with Segmentation (for the full solution take a look to #505)
Proposed solution
We will stop calculating segments if there is not experience is associated with the layout .
How to test it
All manual/funtional tests of Segments and Experiences should work as they did before.
/cc @liferay-echo