-
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-115484 Token definitions API and implementation #111
Conversation
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. |
Converting to draft so that we don't forward it without the Classic's |
ci:test:sf |
ci:test:relevant |
❌ ci:test:sf - 0 out of 1 jobs passed in 3 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-115484 1 Failed Jobs:For more details click here.
|
I don't know why the SF failed... 🤷 |
Jenkins Build:test-portal-source-format#4191 |
ci:test:sf |
❌ ci:test:sf - 0 out of 1 jobs passed in 3 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-115484 1 Failed Jobs:For more details click here.
|
You better figure it out then 😂 |
✔️ 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-115484 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#3942 |
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#91387 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#6666 |
All required test suite(s) passed. |
Closed pull request will not be forwarded. |
Jenkins Build:test-portal-acceptance-pullrequest(master)#6529 |
This PR defines the initial token definitions API and implementation. We will iterate on this PR to refine the API and maybe provide more functionality.
Initially we sent brianchandotcom#91176 to Brian, but he made some objections which led to a full rework of the PR.
The main reasons to rework the PR were:
So, after reviewing the three points we came up with a model where token definitions are associated to OSGi Bundles alone, not related to themes yet (this PR).
In the future we may provide tools to map from themes to OSGi bundles. Even if the existence of a bundle that contains the theme is not enforced by the portal we can define it as a requisite if you want to use token definitions and nothing would break/become inconsistent.
Also, the current API just lists all available token definitions, but doesn't let you query by any criteria. We may add more methods to the
TokenDefinitionRegistry
service in the future to query token definitions as needed.This PR doesn't modify anything in the UI nor does it execute any code (because nobody uses
TokenDefinitionRegistry
yet). However, I have provided units tests to cover almost all production code.In addition, once we add the
token-definition.json
file in classic-theme, I will test it manually to make sure it runs in production too.