diff --git a/docs/include/rpc_introduction.rst.inc b/docs/include/rpc_introduction.rst.inc index 1c9bc2a0cdb9b61f6b8dbf13782b72a9754aa4ed..39a5b023dd20ee2b56013e80b6d361ddd25c8d95 100644 --- a/docs/include/rpc_introduction.rst.inc +++ b/docs/include/rpc_introduction.rst.inc @@ -5,6 +5,10 @@ This page describes the RPCs specific to a particular version of the Tezos proto They are all served under the prefix ``/chains//blocks//``. To make the RPC reference more readable, this prefix is not repeated every time below, but instead shortened as ``../``. +.. warning:: + + Some dynamic or plugin RPCs are not listed here due to a current limitation in the documentation generator. They are listed in the :doc:`../api/openapi` (search the ``.json`` files that are linked from that page). + RPCs - Index ************ diff --git a/docs/index.rst b/docs/index.rst index 690e3d47b7e9e05dc4eb09d3155ca2b7d7745c92..d306ffc25c480320780c37c0a81cf6636a893f4d 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -158,7 +158,7 @@ in the :ref:`introduction `. .. toctree:: :maxdepth: 2 - :caption: kathmandu Kathmandu Protocol doc: + :caption: Kathmandu Protocol doc: kathmandu/protocol kathmandu/glossary diff --git a/docs/protocols/013_jakarta.rst b/docs/protocols/013_jakarta.rst index 29f5ff66bc4246aafaca098efe4330239e616c38..5bd8e358f14e86596f0c7467f9952d88b2badf6b 100644 --- a/docs/protocols/013_jakarta.rst +++ b/docs/protocols/013_jakarta.rst @@ -1,5 +1,5 @@ Protocol Jakarta -================== +================ **Important**: revision `PtJakarta...nGw` of protocol Jakarta contains `two critical bugs `_ diff --git a/scripts/snapshot_alpha.sh b/scripts/snapshot_alpha.sh index af02a6a854d7f164669aba89ad4c708acd2bca50..46df46d39902dfec1333ddbdd074d1c15aec3e71 100755 --- a/scripts/snapshot_alpha.sh +++ b/scripts/snapshot_alpha.sh @@ -120,7 +120,7 @@ doc_index="docs/index.rst" grep -A9999 -F "$alpha_line" "$doc_index" \ | grep -B9999 -F 'toctree' -m1 \ | head -n-1 \ - | sed -e "s/Alpha Development/${label} ${capitalized_label}/g" \ + | sed -e "s/Alpha Development/${capitalized_label}/g" \ -e "s,alpha/,${label}/,g" grep -B9999 -F "$alpha_line" "$doc_index" \ | tac \ diff --git a/src/lib_clic/clic.mli b/src/lib_clic/clic.mli index 3d91842c38dc257baa0503cb32259525fb75352d..f726d8764af8c7abe6e631280522917e2c2ae04b 100644 --- a/src/lib_clic/clic.mli +++ b/src/lib_clic/clic.mli @@ -577,6 +577,10 @@ val restore_formatter : Format.formatter -> formatter_state -> unit (** {2 Parsing and error reporting} *) +(* FIXME: #2935 Add documentation about failures in [Clic] + The documentation should mention what happens if the functions fail. +*) + (** Help error (not really an error), thrown by {!dispatch} and {!parse_global_options}. *) type error += Help : _ command option -> error diff --git a/src/proto_alpha/lib_protocol/sc_rollup_PVM_sem.mli b/src/proto_alpha/lib_protocol/sc_rollup_PVM_sem.mli index 30089681791aabfd8c0c1e8cf1340f7616024156..840dd31ecb4c58df60e0cf03d5db2cd81a5f7d56 100644 --- a/src/proto_alpha/lib_protocol/sc_rollup_PVM_sem.mli +++ b/src/proto_alpha/lib_protocol/sc_rollup_PVM_sem.mli @@ -48,7 +48,7 @@ a given [inbox_level] and contains a given [payload]. According the rollup management protocol, the payload must be obtained - through {!Sc_rollup_inbox_message_repr.to_bytes} which follows a documented + through {!Sc_rollup_inbox_message_repr.serialize} which follows a documented format. *) type input = { inbox_level : Raw_level_repr.t; diff --git a/src/proto_alpha/lib_protocol/sc_rollup_inbox_message_repr.mli b/src/proto_alpha/lib_protocol/sc_rollup_inbox_message_repr.mli index 7611afd6220ae770e956dd157f8dbd89a4abce12..10c4208a1c56653129b4585fcc5f0b1907dfee38 100644 --- a/src/proto_alpha/lib_protocol/sc_rollup_inbox_message_repr.mli +++ b/src/proto_alpha/lib_protocol/sc_rollup_inbox_message_repr.mli @@ -25,7 +25,7 @@ (** This module exposes a type {!t} that represents inbox messages. Inbox messages are produced by the Layer 1 protocol and are encoded using the - {!to_bytes} function, before being added to a smart-contract rollup's inbox. + {!serialize} function, before being added to a smart-contract rollup's inbox. They are part of the [Rollup Management Protocol] that defines the communication protocol for exchanging messages between Layer 1 and Layer 2