-
Notifications
You must be signed in to change notification settings - Fork 0
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-118467 test fix #69
Conversation
…run Shared App Builder scripts on relevant
This reverts commit 3c40430.
…void multiple entries
The configuration wasn't specifically targetting AlloyEditor, but it was only generating valid configuation for that editor. As we are now using CKEditor, those settings were not being properly honored Additionally, only <a> tags were allowed but no attribute, so in practice this editor did not support adding links since their href attributes would've been wiped out on save. This PR addresses this potential bug by adding a[href] to the allowedContent rule configuration
…mins of other companies + SF exceptions & catch and log them to prevent UI error
… from faces repos
… when creating data array
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:sf |
ci:test:relevant |
✔️ 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-118467 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#4378 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#8007 |
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#92247 |
Related issue: https://issues.liferay.com/browse/LPS-118467