[Code Improvement]: Use @use instead of @import in scss files
@Lenni009 is already working on this.
Since May 18, 2023.
Assessment
This issue has not been assessed yet.
Description
Sass writes on their website:
The Sass team discourages the continued use of the @import rule. Sass will gradually phase it out over the next few years, and eventually remove it from the language entirely. Prefer the @use rule instead. (Note that only Dart Sass currently supports @use. Users of other implementations must use the @import rule instead.)
- Dominant language
- TypeScript
- Stars
- 20
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AssistantNMS/WebApp
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
AssistantNMS/WebApp#81 ·
-
Puzzle solutions Openenhancement ready
Difficulty 5/5 Over a week Newbie friendliness 15/100
AssistantNMS/WebApp#6 ·
All issues in AssistantNMS/WebApp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·