fix(tokens): remove style dictionary scripts and reuse oos tokens logic #30786
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number: internal
What is the new behavior?
This pull request updates the design token build system and its dependencies, simplifying the process and removing custom scripts in favor of using the latest features of the
outsystems-design-tokenspackage. The changes modernize how design tokens are generated and maintained, reducing custom code and leveraging upstream improvements.Key changes include:
Build Process Simplification:
core/scripts/tokens/index.mjsandcore/scripts/tokens/utils.mjs) have been removed. Token generation is now handled directly via theoutsystems-design-tokenspackage using annpxcommand in thebuild.tokensscript. This reduces maintenance overhead and keeps the build process aligned with upstream best practices. [1] [2] [3]Dependency Updates:
outsystems-design-tokensto version1.3.3andstyle-dictionaryto version5.1.1in bothpackage.jsonandpackage-lock.json. This ensures compatibility with the latest features and bug fixes and removes the need to specifystyle-dictionarydirectly as a dependency. [1] [2] [3] [4]SCSS Utility Import:
@forward "../../foundations/ionic.utility";statement was removed fromcore/src/css/ionic/utils.bundle.ionic.scss, likely because the utility SCSS is now generated and managed by the new token build process.Removed CSS tests for Ionic theme, as they relied heavily on testing the effect of the utility-classes, that are no longer created on the ionic scope.
Does this introduce a breaking change?