Yicong-Huang opened a new pull request, #5987:
URL: https://github.com/apache/texera/pull/5987

   ### What changes were proposed in this PR?
   
   Dart Sass deprecated `@import` (to be removed in Dart Sass 3.0); the 
frontend build emitted **29** `Sass @import rules are deprecated` warnings 
across 13 dashboard/hub component stylesheets.
   
   These `@import`s only pull shared CSS rules from sibling stylesheets 
(`section-style`, `button-style`, `dashboard.component`, and a few sibling 
`*.component.scss`); no Sass variables, mixins, or functions are referenced 
across files (the only declared variables live inside `section-style.scss` and 
are used only there). So this is a mechanical migration: each `@import "X"` 
becomes `@use "X" as *`, which emits the same CSS in the same order while 
clearing the deprecation.
   
   `as *` is used (rather than the default namespace) because Sass auto-derives 
the namespace from the filename, which is invalid for the dotted names here 
(e.g. `dashboard.component`). Since no members are referenced cross-file, `as 
*` is safe — there are no member collisions.
   
   The plain CSS `@import` in `styles.scss` (`angular-tree-component.css`) is 
intentionally left as-is: it is a CSS import, not a Sass one, and is not 
affected by the deprecation.
   
   ### Any related issues, documentation, discussions?
   
   Closes #5986
   
   ### How was this PR tested?
   
   Ran `ng build` with these changes: Sass compiles cleanly, the **29** 
`@import` deprecation warnings drop to **0**, and the bundle is produced 
normally. CSS output ordering is preserved because the `@import`s were already 
at the top of each file (right after the license header), matching `@use` 
semantics.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Claude Opus 4.8)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to