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
[Freemarker loop size]LPS-124811 #9685
Conversation
…he selected target
… if applies. Database goalTarget keeps the same format
This order was on purpose. Originally we were taking the v= value as everything to the right including parameters which was wrong. With those tests we were ensuring this wouldn't happen again. This reverts commit d0cab88.
…ent scheduled Web Contents by getting their id_ as classPK instead of their resourcePrimKey
…se the user click on the fragment it prevents to play the video and behaves the same than any other fragment
…ntation This basically means that the server will render an empty placeholder and then components (if passed) will be hydrated client-side. Additionally, we introduce a temporary workaround to reduce cumulative layout shift. If a `__placeholder__` property is passed in the `context` object, the renderer will use that instead of an empty placeholder so tag implementors can choose to manually generate it temporarily.
This effectively removes server-side support for Soy rendering, meaning that there won't be an available template manager for soy templates in the server. This doesn't mean that compiled soy templates to JavaScript won't work which reamin as a viable path forward if a developer decides to use them
This markup is used server-side to provide initial markup as a fallback now that we're no longer rendering soy to limit layout cumulative shift when the component hydrates client-side This commit still leaves a slight shift because an empty toolbar has different height than one with content. This is a small adjustment to adress later either by agreeing on a fixed height or by rendering additional elements in the placeholder
…doesn't exist This is necessary because in some contexts the toolbar lacks an ide at this point. This can happen if no id or componentId is set and the toolbar is not linked to a search container
To conserve resources, the PR Tester does not automatically run for every pull. If your code changes were already tested in another pull, reference that pull in this pull so the test results can be analyzed. If your pull was never tested, comment "ci:test" to run the PR Tester for this pull. |
ci:test:relevant |
ci:test:sf |
✔️ ci:test:sf - 1 out of 1 jobs passed in 5 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-124811-1 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#5085 |
✔️ ci:test:stable - 9 out of 9 jobs passed❌ ci:test:relevant - 20 out of 24 jobs passed in 2 hours 8 minutesClick here for more details.Base Branch:Branch Name: master Copied in Private Modules Branch:Branch Name: master-private ci:test:stable - 9 out of 9 jobs PASSED9 Successful Jobs:
ci:test:relevant - 20 out of 24 jobs PASSED4 Failed Jobs:20 Successful Jobs:
For more details click here.Failures unique to this pull:
Failures in common with acceptance upstream results at ff0e5e1:
|
Jenkins Build:test-portal-acceptance-pullrequest(master)#7293 |
No description provided.