Updated to new LabThings structure

.. code-block:: python

    from labthings.server.schema import Schema

    from labthings.server import fields

    from labthings.schema import Schema

    from labthings import fields

    class UserSchema(Schema):

        name = fields.String(required=True)

Basic extension structure

=========================

An extension starts as a simple instance of :py:class:`labthings.server.extensions.BaseExtension`. 

An extension starts as a simple instance of :py:class:`labthings.extensions.BaseExtension`. 

Each extension is described by a single ``BaseExtension`` instance, containing any number of methods, API views, and additional hardware components. 

In order to access the currently running microscope object, use the :py:func:`labthings.server.find.find_component` function, with the argument ``"org.openflexure.microscope"``. Likewise, any new components attached by other extensions can be found using their full name, as above.

In order to access the currently running microscope object, use the :py:func:`labthings.find_component` function, with the argument ``"org.openflexure.microscope"``. Likewise, any new components attached by other extensions can be found using their full name, as above.

A simple extension file, with no API views but application-available methods may look like:

.. code-block:: python

    from labthings.server.find import find_extension

    from labthings import find_extension

    def test_extension_method():

        # Find your extension. Returns None if it hasn't been found.

Subclassing ``BaseExtension``

-------------------------------

The syntax used above allows novice programmers to easily start building extensions, without having to deal with subclassing. However, for more complex extensions which require persistent state, subclassing :py:class:`labthings.server.extensions.BaseExtension` is recommended.

The syntax used above allows novice programmers to easily start building extensions, without having to deal with subclassing. However, for more complex extensions which require persistent state, subclassing :py:class:`labthings.extensions.BaseExtension` is recommended.

The same simple extension as seen above can be written using subclassing:

.. code-block:: python

    ...

    from labthings.server.view import ActionView

    from labthings import ActionView

    class SlowAPI(ActionView):

        def post(self):

    def close(self):

        logging.debug(self.fp.name)

        self.fp.close()

        if os.path.exists(self.fp.name):

            os.unlink(self.fp.name)

        assert not os.path.exists(self.fp.name)

{

  "name": "openflexure-microscope-jsclient",

  "version": "2.3.0",

  "version": "2.4.0",

  "lockfileVersion": 1,

  "requires": true,

  "dependencies": {