From 7c04b5e250f30cde5bb346b24fbda276742d2b5a Mon Sep 17 00:00:00 2001 From: Natalie Weizenbaum Date: Mon, 24 Sep 2018 13:51:48 -0700 Subject: [PATCH] [Module System] Clarify that `@forward` includes the module's CSS --- proposal/module-system.changes.md | 4 ++++ proposal/module-system.md | 5 +++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/proposal/module-system.changes.md b/proposal/module-system.changes.md index 5429f32a..37f1078f 100644 --- a/proposal/module-system.changes.md +++ b/proposal/module-system.changes.md @@ -1,3 +1,7 @@ +## Draft 3 + +* Clarify that `@forward` includes the forwarded module's CSS tree. + ## Draft 2.1 * Make sure nested `@import`s preserve the parent selector/at-rule context of diff --git a/proposal/module-system.md b/proposal/module-system.md index ca124cfe..e6f27d27 100644 --- a/proposal/module-system.md +++ b/proposal/module-system.md @@ -1,4 +1,4 @@ -# The Next-Generation Sass Module System: Draft 2.1 +# The Next-Generation Sass Module System: Draft 3 *([Issues](https://github.com/sass/sass/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A%22%40use%22), [Changelog](module-system.changes.md))* @@ -901,7 +901,8 @@ The [`@forward`](#forward) rule forwards another [module](#module)'s public API as though it were part of the current module's. > Note that `@forward` *does not* make any APIs available to the current module; -> that is purely the domain of `@use`. +> that is purely the domain of `@use`. However, it *does* include the forwarded +> module's CSS tree. First, we define a general procedure for forwarding a module `module` with a `@forward` rule `rule`: