Hi,
Ivan, I like your suggestion. To me it looks better than the current
approach.
Best Regards,
Igor
On Mon, Apr 26, 2021 at 11:47 AM Nikita Safonov
wrote:
> Hi Ivan,
>
> Thanks for sharing the information.
> I'll look through the docs and share my thoughts and suggestions soon.
>
> Regards,
Hi Ivan,
Thanks for sharing the information.
I'll look through the docs and share my thoughts and suggestions soon.
Regards,
Nikita
пт, 23 апр. 2021 г. в 14:06, Ivan Daschinsky :
> Hi, Nikita! Thanks for support.
>
> As developers of thin client, we also would try to update
> documentation as
Hi, Nikita! Thanks for support.
As developers of thin client, we also would try to update
documentation as soon as possible.
For example, recently I've merged to master expiry policy support for
python thin client and documentation was updated simultaneously [2][3]
I am planning to update documen
Hi Ivan,
Thank you for the suggestion.
I agree that Ignite main docs on thin clients probably need a clean-up to
be kept up-to-date.
And migrating the key information to readthedocs.io is really an option.
Let's see what other Igniters think about this idea.
I'd be glad if Igor Gusev could shar
Igniters, there are some questions regarding the documentation state
of thin clients.
Recently, we have released pyignite 0.4.0. Traditionally,
documentation for python thin client is autogenerated from source and
contains in the same git repository, as the client itself.
Documentation is autogene
