d6f79edae2
- start using `GET` and query parameters instead of `POST` when meaningful - inline parsed protocol data and metadata in block headers - inline parsed protocol data and metadata in operations - split the RPC in four categories: - static data, available explicitly in block headers and operations - static "metadata", information that were computed while validating a block or an operation, but which are not explicit in the block header (e.g. the baker of a block, the list of internal transfer... (currently not implemented, but that's WIP)) - "context" all the static data we may read in the context (contracts balance, list of delegates, ...) - "helpers" are some RPC that may perform some computation. |
||
---|---|---|
.. | ||
_extensions | ||
api | ||
doc_gen | ||
introduction | ||
tutorials | ||
whitedoc | ||
conf.py | ||
index.rst | ||
logo.svg | ||
Makefile | ||
README.rst |
****************************** Building documentation locally ****************************** The documentation is available online at `doc.tzalpha.net <http://doc.tzalpha.net/>`_, always up to date with master on `GitLab <https://gitlab.com/tezos/tezos>`_. Building instructions --------------------- To build the documentation, you can use the main Makefile target ``doc-html`` .. code:: bash make doc-html The documentation is built by Sphinx, and uses the Read The Docs theme. On a debian system, you can install the needed dependencies with: .. code:: bash sudo apt install \ python3-recommonmark \ python3-sphinx \ python3-sphinx-rtd-theme Sphinx extensions ----------------- Some ad-hoc reference kinds are supported. - ``:package-src:`name``` or ``:package-src:`text<name>``` points to the gitlab source tree viewer where the `.opam` for the package is located - ``:package:`name``` or ``:package:`text<name>``` now points either to the `odoc` page, or if it doesn't exist, to the gitlab source tree viewer - ``:package-name:`name``` or ``:package-name:`text<name>``` just displays the package name (no link), checking that the package exists - ``:src:`/path/to/file/or/dir``` or ``:src:`text</path/to/file/or/dir>``` points to the gitlab source tree viewer - ``:opam:`package``` or ``:opam:`text<package>``` points to the package page on ``opam.ocaml.org``, version number is supported (``package.version``) OCaml documentation ------------------- Odoc is used for OCaml API generation, that you can install with: .. code:: bash opam install odoc Tezos generates the API documentation for all libraries in HTML format. The generated HTML pages in ``_build/<context>/_doc``. It creates one sub-directory per public library and generates an ``index.html`` file in each sub-directory. The documentation is not installed on the system by Tezos. It is meant to be read locally while developing and then published on the www when releasing packages.