You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would open up possibilities for multiclient applications to have independent logging for each client. In my honest opinion this also makes more sense architecture wise, as all properties in Helpers class are bound to client and there is no need for putting them into separate class
The text was updated successfully, but these errors were encountered:
I disagree with your analysis. All properties/members of Helper class are absolutely not bound to Client, and perfectly fine as static.
The only problem I recognize is about logging.
Now there are two reasons I will not move Log to Client:
I need to be able to log from various methods that are not Client-bound, like Session, Encryption and TL serialization
I don't feel the need to particularly help those developers that want to use multiple Clients in their program, as mass-managing fake user profiles goes against Telegram TOS
This would open up possibilities for multiclient applications to have independent logging for each client. In my honest opinion this also makes more sense architecture wise, as all properties in Helpers class are bound to client and there is no need for putting them into separate class
The text was updated successfully, but these errors were encountered: