From b2ab9cbe50c2fde03deedb69b2752199c5837c98 Mon Sep 17 00:00:00 2001 From: Natalie Weizenbaum Date: Fri, 11 Oct 2019 14:09:31 -0700 Subject: [PATCH] Recommend that users write @forward before @use (#384) --- source/documentation/at-rules/forward.html.md.erb | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/source/documentation/at-rules/forward.html.md.erb b/source/documentation/at-rules/forward.html.md.erb index c0804c4..cdeff3a 100644 --- a/source/documentation/at-rules/forward.html.md.erb +++ b/source/documentation/at-rules/forward.html.md.erb @@ -17,6 +17,13 @@ module once! [public]: use#private-members +If you *do* write both a `@forward` and a `@use` for the same module in the same +file, it's always a good idea to write the `@forward` first. That way, if your +users want to [configure the forwarded module][], that configuration will be +applied to the `@forward` before your `@use` loads it without any configuration. + +[configure the forwarded module]: use#configuring-modules + <% fun_fact do %> The `@forward` rule acts just like `@use` when it comes to a module's CSS. Styles from a forwarded module will be included in the compiled CSS output,