fix Template.api.{call,apply} conflicting with methods in docs, breka…

…ing IE
shama · Apr 5, 2012 · 42f908a · 42f908a
1 parent 5d0388c
commit 42f908a
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/docs/client/api.html b/docs/client/api.html
@@ -219,7 +219,7 @@ <h2 id="methods_header"><span>Methods</span></h2>
 function throws a different exception, then it will be mapped to
 `Meteor.Error(500, "Internal server error")` on the wire.
 
-{{> api_box call}}
+{{> api_box meteor_call}}
 
 This is how to invoke a method.  It will run the method on the server.
 If a stub is available, it will also run the stub on the client.
@@ -267,7 +267,7 @@ <h2 id="methods_header"><span>Methods</span></h2>
 their "real" versions that update the database (using credentials known
 only to the server.)
 
-{{> api_box apply}}
+{{> api_box meteor_apply}}
 
 `Meteor.apply` is just like `Meteor.call`, but it allows the
 arguments to be passed as an array.

diff --git a/docs/client/api.js b/docs/client/api.js
@@ -193,7 +193,7 @@ Template.api.error = {
   ]
 };
 
-Template.api.call = {
+Template.api.meteor_call = {
   id: "meteor_call",
   name: "Meteor.call(func, arg1, arg2, ... [, asyncCallback])",
   locus: "Anywhere",
@@ -211,7 +211,7 @@ Template.api.call = {
   ]
 };
 
-Template.api.apply = {
+Template.api.meteor_apply = {
   id: "meteor_apply",
   name: "Meteor.apply(name, params [, asyncCallback])",
   locus: "Anywhere",