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: src/sdk-reference/js/6/extend-sdk/index.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,8 @@ order: 410
7
7
8
8
# Extend the SDK with a custom SDK controller
9
9
10
+
{{{since "6.1.1"}}}
11
+
10
12
It is possible to extend the SDK's API by adding new controllers.
11
13
12
14
These controllers correspond to [custom controllers created in a plugin]({{ site_base_path }}plugins/1/essentials/controllers). Thus, it is possible to use the actions of a core plugin in the SDK in the same way as the other actions of the Kuzzle API.
@@ -23,7 +25,7 @@ After defining your new controller based on `BaseController`, you can add it to
23
25
24
26
The constructor of a custom SDK controller will be called by passing the SDK instance to it. It must call the parent constructor with this instance of the SDK and its name as defined in the API.
25
27
26
-
For instance, if there is a plugin named `nyc-open-data-taxi`, extending Kuzzle's API with the following controller:
28
+
For instance, if there is a plugin named `nyc-open-data-plugin`, extending Kuzzle's API with the following controller:
0 commit comments