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
sphinx-autodoc2 gives difficult-to-follow errors that don't easily show where in the source they come from.
I've set up flake8 to lint the docstrings, and fixed the errors. I've also fixed my links, which used incorrect syntax for `:ref:` links.
I may try out sphinx.ext.autodoc instead - this imports the module, but might be more reliable.
Copy file name to clipboardExpand all lines: docs/source/lt_core_concepts.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ The server API is accessed over an HTTP requests, allowing client code (see belo
15
15
Everything is a Thing
16
16
---------------------
17
17
18
-
As described in wot_cc_, a Thing represents a piece of hardware or software. LabThings-FastAPI automatically generates a wot_td_ to describe each Thing. Each function offered by the Thing is either a Property or Action (LabThings-FastAPI does not yet support Events). These are termed "interaction affordances" in WoT_ terminology.
18
+
As described in :ref:`wot_cc`, a Thing represents a piece of hardware or software. LabThings-FastAPI automatically generates a :ref:`wot_td` to describe each Thing. Each function offered by the Thing is either a Property or Action (LabThings-FastAPI does not yet support Events). These are termed "interaction affordances" in WoT_ terminology.
19
19
20
20
Code on the LabThings FastAPI Server is composed of Things, however these can call generic Python functions/classes. The entire HTTP API served by the server is defined by `.Thing` objects. As such the full API is composed of the actions and properties (and perhaps eventually events) defined in each Thing.
Copy file name to clipboardExpand all lines: docs/source/using_things.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,9 +28,9 @@ One goal of LabThings-FastAPI is to make code portable between a client (e.g. a
28
28
29
29
A `.DirectThingClient` class will call actions and properties of other `.Thing` subclasses using the same interface that would be used by a remote client, which means code for an action may be developed as an HTTP client, for example in a Jupyter notebook, and then moved to the server with minimal changes. Currently, there are a few differences in behaviour between working locally or remotely, most notably the return types (which are usually Pydantic models on the server, and currently dictionaries on the client). This should be improved in the future.
30
30
31
-
It is also possible for a `.Thing` to access other `.Thing` instances directly. This gives access to functionality that is only available in Python, i.e. not available through a `.ThingClient` over HTTP. However, the `.Thing` must then be supplied manually with any dependencies_ required by its actions, and the public API as defined by the wot_td_ is no longer enforced.
31
+
It is also possible for a `.Thing` to access other `.Thing` instances directly. This gives access to functionality that is only available in Python, i.e. not available through a `.ThingClient` over HTTP. However, the `.Thing` must then be supplied manually with any :ref:`dependencies` required by its actions, and the public API as defined by the :ref:`wot_td` is no longer enforced.
32
32
33
-
Actions that make use of other `.Thing` objects on the same server should access them using dependencies_.
33
+
Actions that make use of other `.Thing` objects on the same server should access them using :ref:`dependencies`.
0 commit comments