From e2bb5f2dfd55ecd3166e656537bb0f3bcad009b4 Mon Sep 17 00:00:00 2001 From: Denilson Date: Wed, 19 Oct 2022 09:37:16 -0300 Subject: [PATCH] Update guide/source/2.8-migration.md Co-authored-by: Frederico Maia --- guide/source/2.8-migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/source/2.8-migration.md b/guide/source/2.8-migration.md index e5d58dee05..75fe246bd0 100644 --- a/guide/source/2.8-migration.md +++ b/guide/source/2.8-migration.md @@ -84,7 +84,7 @@ As said before, the `callAsync` should be used to call async methods. We do not consider this version of the `callAsync` as the final product. It has its limitations when your methods have a [stub](https://docs.meteor.com/api/methods.html#:~:text=was%20received%20on.-,Calling,and%20you%E2%80%99ll%20have%20to%20wait%20for%20the%20results%20from%20the%20server.,-If%20you%20do), and it should be used where you know it won't affect other parts of your application. -We'll continue working on it to find a solution where these limitations don't exist. +> We will revisit these limitations soon and try to find a solution where these limitations do not exist.

The callAsync limitations