-
Notifications
You must be signed in to change notification settings - Fork 1
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-115485 As a developer I can inject custom CSS variables declaring an OSGi component #21
Conversation
…lues All instances of ScopedCSSVariablesProvider will be queried whenever a page's HTML is rendered to gather all the ScopedCSSVariables that must be injected in the page. A ScopedCSSVariables object defines a set of CSS variable values tied to a given CSS scope (f.e: :root, body, etc...)
…viders This DynamicInclude renders all ScopedCSSVariables in the <head> tag of the page's HTML right after the theme's CSS links are injected.
ci:test:sf |
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 |
...ntend/css/variables/web/internal/servlet/taglib/ScopedCSSVariablesTopHeadDynamicInclude.java
Outdated
Show resolved
Hide resolved
✔️ ci:test:sf - 1 out of 1 jobs passed in 4 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-115485 1 Successful Jobs:For more details click here. |
...ntend/css/variables/web/internal/servlet/taglib/ScopedCSSVariablesTopHeadDynamicInclude.java
Show resolved
Hide resolved
@izaera Maybe the OSGi API already takes care of this with the cardinality stuff, but let me ask: Is there a way for devs to specify some kind of priority in case they want to override variables already declared by some other previously deployed |
On the other PR @john-co flagged one of the test failures as likely related, and indeed it does look that way. Assigning back to you @izaera to address. |
.../com/liferay/frontend/css/variables/web/internal/servlet/taglib/liferay_css_variables_1.html
Outdated
Show resolved
Hide resolved
Good question. I think the Should I use |
I think |
Test still failing @izaera 😢 |
It doesn't compile 😭 |
ci:test:relevant |
Forwarding this as discussed with @jbalsas in a slack conversation. |
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: |
✔️ 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-115485 1 Successful Jobs:For more details click here. |
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#90496 |
Previously: https://github.com/wincent/liferay-portal/pull/354
Moving it here and will try to get a green
ci:test:relevant
run out of it.cc @izaera
Original description follows:
This is a partial PR based on the original PoC https://github.com/jbalsas/liferay-portal/pull/2211. This implements the Frontend Infrastructure DynamicInclude part only, and provides tests for it.
Note that there's no way to test this from the GUI.