Overview
========

.. module:: koda_validate
    :noindex:

At its core, Koda Validate is little more than a few function signatures (see
:ref:`philosophy/validators:Validators`, :ref:`philosophy/predicates:Predicates`,
:ref:`philosophy/coercion:Coercion`, and :ref:`philosophy/processors:Processors`), which
can be combined to build validators of arbitrary complexity. This simplicity also
provides straightforward paths for:

- optimization: Koda Validate tends to be fast (for Python)
- extension: Koda Validate can be extended to Validate essentially anything, even asynchronously.

.. note::

    If you've run into edge cases that you can't work around in other validation libraries, please
    take a look at Extension. The simplest way to work around :class:`Validator` quirks in Koda Validate
    is often to write your own.

Flexible
--------
:class:`Validator`\s, :class:`Predicate`\s, :class:`Coercer`\s, and :class:`Processor`\s in Koda Validate are not coupled with
any specific framework, serialization format, or language. Instead Koda Validate aims to make it
straightforward to contextualize validation outputs and artifacts -- by writing *interpreters* that
consume a :class:`Validator` and produce some output. This effectively makes Koda Validate just as easy to
work with in any framework, format or language. More info is available at :ref:`how_to/metadata:Metadata`.