update docstrings

[PatrickAlphaC]

We use a lot of auto-doc features, where our reference docs are created based on the doc strings of our functions. For most of the "important" stuff like:

• Networks
• _Networks
• Config
• MoccasinAccount
• NamedContracts

We should have better docstrings for our docs to auto-generate

[s3bc40]

Should we use the default doc string format from Sphinx?

EDIT: yes we should to respect the compatibility with reStructuredText. I tried to add napoleon in extensions of conf.py but there were errors like this during the docs generation:

/home/s3bc40/mox-cu/moccasin/moccasin/config.py:docstring of moccasin.config.Config.dependencies:1: WARNING: duplicate object description of moccasin.config.Config.dependencies, other instance in api_reference/config_reference, use :no-index: for one of them
/home/s3bc40/mox-cu/moccasin/moccasin/config.py:docstring of moccasin.config.Config.extra_data:1: WARNING: duplicate object description of moccasin.config.Config.extra_data, other instance in api_reference/config_reference, use :no-index: for one of them
/home/s3bc40/mox-cu/moccasin/moccasin/config.py:docstring of moccasin.config.Config.networks:1: WARNING: duplicate object description of moccasin.config.Config.networks, other instance in api_reference/config_reference, use :no-index: for one of them
/home/s3bc40/mox-cu/moccasin/moccasin/config.py:docstring of moccasin.config.Config.project:1: WARNING: duplicate object description of moccasin.config.Config.project, other instance in api_reference/config_reference, use :no-index: for one of them
None:11: ERROR: Unexpected indentation. [docutils]

I see in the moccasin venv/lib we have sphinxcontrib without napoleon inside, which is required to use Google or NumPy style.

I saw some doc string were written in Google style, but I don't know if it is the way to go...

I'll test with the default Sphinx typo.

---

Also making a list in case people wants to contribute to avoid duplicate:

• NamedContract -> @s3bc40 -> PR
• MoccasinAccount -> @s3bc40 -> PR
• Config -> @s3bc40 -> PR
• Network -> @s3bc40 -> PR
• _Networks -> @s3bc40 -> PR

---

Do I have to create a dedicated branch to this issue from my fork repo, and group all other doc branch before going into main?