You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@weex.apache.org by zs...@apache.org on 2019/01/02 02:54:21 UTC

[incubator-weex-site] branch draft updated: Update weex-variable.md

This is an automated email from the ASF dual-hosted git repository.

zshshr pushed a commit to branch draft
in repository https://gitbox.apache.org/repos/asf/incubator-weex-site.git


The following commit(s) were added to refs/heads/draft by this push:
     new 78c9763  Update weex-variable.md
78c9763 is described below

commit 78c9763a0f3e13ef998c7871657472240bc94908
Author: zshshr <zh...@gmail.com>
AuthorDate: Wed Jan 2 10:54:17 2019 +0800

    Update weex-variable.md
---
 docs/docs/api/weex-variable.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/api/weex-variable.md b/docs/docs/api/weex-variable.md
index 4062929..36d9f16 100644
--- a/docs/docs/api/weex-variable.md
+++ b/docs/docs/api/weex-variable.md
@@ -75,7 +75,7 @@ This API is mainly used inside of the Vue and Rax framework to convert the virtu
 
 ## `requireModule`
 
-For those features which does not rely on the UI, Weex wraps them into **modules**. It is a way to access native capabilities in javascript. Except for the [built-in modules](../modules/), it's quite easy to integrate the existing native modules to Weex platform. After that, you can use `weex.requireModule` to require both customized and built-in modules.
+For those features which does not rely on the UI, Weex wraps them into **modules**. It is a way to access native capabilities in javascript. Except for the [built-in modules](../modules/animation.html), it's quite easy to integrate the existing native modules to Weex platform. After that, you can use `weex.requireModule` to require both customized and built-in modules.
 
 ```typescript
 weex.requireModule(name: string): Object | void;