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-144391 search-experiences-web: Return full element JSON when clicking on 'View Element JSON' #379
LPS-144391 search-experiences-web: Return full element JSON when clicking on 'View Element JSON' #379
Conversation
…king on 'View Element JSON'
CI is automatically triggering the following test suites:
|
✔️ 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-144391-view-element-JSON 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#2205 Jenkins Report:jenkins-report.html Jenkins Suite:sf Pull Request:liferay-search#379 Testray Routine:EE Pull Request Testray Importer:publish-testray-report#8172 |
❌ ci:test:search - 11 out of 14 jobs passed in 1 hour 35 minutesClick here for more details.Base Branch:Branch Name: master Upstream Comparison:Branch GIT ID: fc0df1a3be0b5b6d4a1ed1680580676457a03816 ci:test:search - 11 out of 14 jobs PASSED3 Failed Jobs:11 Successful Jobs:
For more details click here.Failures unique to this pull:
Failures in common with acceptance upstream results at fc0df1a:
Test bundle downloads:
|
Jenkins Build:test-portal-acceptance-pullrequest(master)#2782 Jenkins Report:jenkins-report.html Jenkins Suite:search Pull Request:liferay-search#379 Testray Routine:EE Pull Request Testray Importer:publish-testray-report#8017 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just that one small doc correction.
Looks good though! I'm definitely in favor of this specific function with clear documentation of its purpose. I also appreciate you putting the formatting changes in a separate commit. 💯
...-experiences-web/src/main/resources/META-INF/resources/sxp_blueprint_admin/js/utils/utils.js
Outdated
Show resolved
Hide resolved
@oliv-yu You can run ci:forward once you make that doc change. Thanks! |
ci:forward |
CI is automatically triggering the following test suites:
The pull request will automatically be forwarded to the user
|
✔️ 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-144391-view-element-JSON 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#1981 Jenkins Report:jenkins-report.html Jenkins Suite:sf Pull Request:liferay-search#379 Testray Routine:EE Pull Request Testray Importer:publish-testray-report#6996 |
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#115390 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#828 Jenkins Report:jenkins-report.html Jenkins Suite:relevant Pull Request:liferay-search#379 Testray Routine:EE Pull Request Testray Importer:publish-testray-report#1945 |
https://issues.liferay.com/browse/LPS-144391 - "View Element JSON" should return the full JSON of the Element (with replaced variables)
Notes:
getSXPElementJSON
insideutil.js
so as not to clutter the SXPElement componentThanks for taking a look!