<commit_before>*************************************
:mod:`mopidy.backends` -- Backend API
*************************************

.. automodule:: mopidy.backends
    :synopsis: Backend interface.
    :members:<commit_msg>docs: Add note on what the backend API docs covers. Add graph of backend controller relations.<commit_after>**********************
:mod:`mopidy.backends`
**********************

The backend and its controllers
===============================

.. graph:: backend_relations

    backend -- current_playlist
    backend -- library
    backend -- playback
    backend -- stored_playlists


Backend API
===========

.. note::

    Currently this only documents the API that is available for use by
    frontends like :class:`mopidy.mpd.handler`, and not what is required to
    implement your own backend. :class:`mopidy.backends.BaseBackend` and its
    controllers implements many of these methods in a matter that should be
    independent of most concrete backend implementations, so you should
    generally just implement or override a few of these methods yourself to
    create a new backend with a complete feature set.

.. automodule:: mopidy.backends
    :synopsis: Backend interface.
    :members:
{'fraction_non_alphanumeric': 0.19020408163265307, 'fraction_numerical': 0.0, 'mean_word_length': 4.239316239316239, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4771394', 'n_tokens_mistral': 307, 'n_tokens_neox': 295, 'n_words': 120}