You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,19 +25,19 @@ Of course, in an extremely high concurrent scenario, the parallel call interface
25
25
26
26
-**Unlimited nesting**
27
27
28
-
Dependencies support deep nesting. The follow example has only one layer nesting relationship.
28
+
Dependencies support deep nesting. The following example has only one layer of nesting relationship.
29
29
30
30
-**Exception handling**
31
31
32
32
Currently supports two processing methods: ignore or stop
33
33
34
34
Ignore means that the provider method ignores the exception and returns a null value when it is executed. Stop means that once a provider method throws an exception, it will be thrown up step by step, and stop subsequent processing.
35
35
36
-
Exception handling configuration item supports consumer level or global level, and comsumer level is priority to global level
36
+
Exception handling configuration item supports consumer level or global level, and consumer level is priority to global level
37
37
38
38
-**Query Cache**
39
39
40
-
In one query life cycle of calling the Facade's query method, the result called by DataProvider method may be reused. As long as the method signature and the parameters are consistent, the default method is idempotent, and the cached query result will be used directly.** However, this Not an absolute. Considering the multi-threading feature, sometimes the cache is not used.
40
+
In one query life cycle of calling the Facade's query method, the result called by `@DataProvider` method may be reused. As long as the method signature and the parameters are consistent, the default method is idempotent, and the cached query result will be used directly.** However, this Not an absolute. Considering the multi-threading feature, sometimes the cache is not used.
41
41
42
42
-**Timeout Control**
43
43
@@ -83,7 +83,7 @@ Developing a user summary data interface that includes the user's basic informat
83
83
84
84
### 1. Define an "atomic" service to provide user data
85
85
86
-
Use `@DataProvider` to define the interface a data provider.
86
+
Use `@DataProvider` to define the interface as a data provider.
87
87
88
88
Use `@InvokeParameter` to specify the input parameters to pass.
89
89
@@ -128,7 +128,7 @@ User user = DataFacade.get(
128
128
}
129
129
});
130
130
Assert.notNull(user,"User must not be NULL");
131
-
Assert.notNull(user.getPosts(),"User posts must not be NULL");
131
+
Assert.notNull(user.getPosts(),"User's posts must not be NULL");
132
132
```
133
133
134
134
#### Method2:Define and implement an aggregation layer
@@ -156,7 +156,7 @@ User user = DataFacade.get(/*data id*/ "userWithPosts",
156
156
Collections.singletonMap("userId",1L),
157
157
User.class);
158
158
Assert.notNull(user,"User must not be NULL");
159
-
Assert.notNull(user.getPosts(),"User posts must not be NULL");
159
+
Assert.notNull(user.getPosts(),"User's posts must not be NULL");
0 commit comments