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
{{ message }}
This repository was archived by the owner on Jun 1, 2025. It is now read-only.
The HTML comments below are for your reference, and are not displayed
5
+
when your issue is submitted, feel free to leave them.
6
+
7
+
CHOOSE the relevant headings, DELETE the other(s).
8
+
-->
9
+
**I'm submitting a bug report**
10
+
**I'm submitting a feature request**
11
+
12
+
***Library Version:**
13
+
major.minor.patch
14
+
15
+
<!--
16
+
If you think the environment might have an influence then please provide
17
+
else you can omit.
18
+
-->
19
+
**Please tell us about your environment:**
20
+
***Operating System:**
21
+
OSX 10.x|Linux (distro)|Windows [7|8|8.1|10]
22
+
23
+
24
+
***Browser:**
25
+
all | Chrome XX | Firefox XX | Edge XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView
26
+
27
+
***Language:**
28
+
TypeScript X.X
29
+
30
+
31
+
**Current behavior:**
32
+
33
+
34
+
**Expected/desired behavior:**
35
+
36
+
37
+
***What is the expected behavior?**
38
+
39
+
40
+
***What is the motivation / use case for changing the behavior?**
* Define what our internal Post Process callback, it will execute internally after we get back result from the Process backend call
281
-
* For now, this is GraphQL Service only feautre and it will basically refresh the Dataset & Pagination without having the user to create his own PostProcess every time
277
+
* For now, this is GraphQL Service only feature and it will basically refresh the Dataset & Pagination without having the user to create his own PostProcess every time
0 commit comments