-Since now, generic models are being used as request bodies for various requests. But this is creating ambiguity for users that do not have the full knowledge of the telegram bot API documentation. For example, entity.MessageEnvelop is used for many functions - so it has many fields that are used at some function but not in another - how can someone new know these differences? So, in my opinion, it is better to have separate models for each function (even if it means there will be some code duplication).
-Since now, generic models are being used as request bodies for various requests. But this is creating ambiguity for users that do not have the full knowledge of the telegram bot API documentation. For example,
entity.MessageEnvelopis used for many functions - so it has many fields that are used at some function but not in another - how can someone new know these differences? So, in my opinion, it is better to have separate models for each function (even if it means there will be some code duplication).