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: developer_manual/digging_deeper/api.rst
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,3 +7,24 @@ PHP public API
7
7
8
8
The public API is contained in the OCP namespace. See the `OCP API reference
9
9
<https://nextcloud-server.netlify.app/>`_ for further details.
10
+
11
+
12
+
PHP unstable API
13
+
----------------
14
+
15
+
To avoid releasing incomplete public API, it is possible to release a
16
+
first version of the future API in the `NCU` namespace, following these rules:
17
+
18
+
- Files are located in ``/lib/unstable/``
19
+
- Code quality, comments, tests and psalm check are expected to be identical to the `OCP` namespace.
20
+
- Classes must be tag as ``@experimental``, including the current version of Nextcloud.
21
+
- Code from the `OCP` namespace must never mention anything coming from the `NCU` namespace. It can not require it as an argument, constant or return something from `NCU`.
22
+
- An API can only live in this unstable namespace for one major release.
23
+
- During this testing phase, the code and the API can be modified/restructured without limitation.
24
+
- API within the testing namespace must have up-to-date documentation.
25
+
- If accepted, the API will be copied to the `OCP` public namespace.
26
+
- Once tested, the version from the `NCU` namespace will be marked as deprecated.
27
+
- Deprecated API from the `NCU` namespace are kept for 2 major releases.
28
+
29
+
.. note::
30
+
- API from `NCU` are included to the ``nextcloud-deps/OCP`` package for easier testing with psalm
0 commit comments