Repository navigation
chore: Fixes internal build error caused by new styling mixin imports in test pages - #5170
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5170 +/- ##
=======================================
Coverage 97.73% 97.73%
=======================================
Files 996 996
Lines 32178 32178
Branches 11872 11872
=======================================
Hits 31449 31449
Misses 723 723
Partials 6 6 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
pan-kot
marked this pull request as ready for review
October 21, 2026 16:04
pan-kot
enabled auto-merge
October 21, 2026 16:36
SpyZzey
approved these changes
Oct 22, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
#5165 introduced new Sass utils imports in test pages. The test pages are built separately in the internal pipeline - causing issues due to local
../../lib/exports no longer resolvable. This is addressed by aliasing these imports - same as it works today for design tokens.How has this been tested?
Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness
CONTRIBUTING.md.CONTRIBUTING.md.Security
checkSafeUrlfunction.Testing
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.