Added more details about the use of configuration fragments in Skylark to the documentation.

--
MOS_MIGRATED_REVID=101357875

1 files changed, 8 insertions, 1 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/rules/SkylarkRuleContext.java b/src/main/java/com/google/devtools/build/lib/rules/SkylarkRuleContext.java
index 93ff5aa416..dbaf2c8f64 100644
--- a/src/main/java/com/google/devtools/build/lib/rules/SkylarkRuleContext.java
+++ b/src/main/java/com/google/devtools/build/lib/rules/SkylarkRuleContext.java
@@ -312,7 +312,14 @@ public final class SkylarkRuleContext {
   }
 
   @SkylarkCallable(
-      name = "fragments", structField = true, doc = "Allows access to configuration fragments.")
+    name = "fragments",
+    structField = true,
+    doc =
+        "Allows access to configuration fragments. Possible fields are <code>cpp</code>, "
+            + "<code>java</code> and <code>jvm</code>. "
+            + "However, rules have to declare their required fragments in order to access them "
+            + "(see <a href=\"../rules.html#fragments\">here</a>)."
+  )
   public FragmentCollection getFragments() {
     return fragments;
   }