httk.web.templating.base
========================

.. py:module:: httk.web.templating.base


Classes
-------

.. autoapisummary::

   httk.web.templating.base.TemplateRenderInput
   httk.web.templating.base.TemplateEngine


Module Contents
---------------

.. py:class:: TemplateRenderInput

   .. py:attribute:: content_html
      :type:  str


   .. py:attribute:: template_name
      :type:  str | None


   .. py:attribute:: base_template_name
      :type:  str | None


   .. py:attribute:: context
      :type:  dict[str, object]


.. py:class:: TemplateEngine

   Bases: :py:obj:`Protocol`


   Base class for protocol classes.

   Protocol classes are defined as::

       class Proto(Protocol):
           def meth(self) -> int:
               ...

   Such classes are primarily used with static type checkers that recognize
   structural subtyping (static duck-typing).

   For example::

       class C:
           def meth(self) -> int:
               return 0

       def func(x: Proto) -> int:
           return x.meth()

       func(C())  # Passes static type check

   See PEP 544 for details. Protocol classes decorated with
   @typing.runtime_checkable act as simple-minded runtime protocols that check
   only the presence of given attributes, ignoring their type signatures.
   Protocol classes can be generic, they are defined as::

       class GenProto[T](Protocol):
           def meth(self) -> T:
               ...


   .. py:method:: render(render_input: TemplateRenderInput) -> str


   .. py:method:: render_fragment(*, template_name: str, context: dict[str, object]) -> str | None