From ea381f0c8a103936e00a07b79a6ca8f8c81f2819 Mon Sep 17 00:00:00 2001 From: Vladimir Moskva Date: Fri, 5 Aug 2016 16:48:07 +0000 Subject: Added a design document and fixed links -- Change-Id: I1a904d19e1a63eff8c245bac3c18eb4ce9838912 Reviewed-on: https://bazel-review.googlesource.com/#/c/4271/ MOS_MIGRATED_REVID=129451413 --- site/designs/_posts/2016-08-04-extensibility-for-native-rules.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'site/designs/_posts') diff --git a/site/designs/_posts/2016-08-04-extensibility-for-native-rules.md b/site/designs/_posts/2016-08-04-extensibility-for-native-rules.md index ed5877e4ee..7a70b17c1c 100644 --- a/site/designs/_posts/2016-08-04-extensibility-for-native-rules.md +++ b/site/designs/_posts/2016-08-04-extensibility-for-native-rules.md @@ -40,7 +40,7 @@ and suggest some practical steps we can take to get there. ## Extensible Native Rules This proposal assumes [Declared Providers -](/designs/declared-providers.html) +](/designs/skylark/declared-providers.html) are implemented. Here is how the implementation of bread\_library might look like: @@ -151,4 +151,3 @@ with internal API. Through the execution of this phase, more and more use cases are covered, and at the end the rules are fully extensible. - -- cgit v1.2.3