GoTGProto v1.0.0-beta10
GoTGProto Changelog
- Updated GoTD to v0.82.0
- Deprecated
ctx.ForwardMessage
(Usectx.ForwardMessages
now) - Replaced BigCache with Cacher for cache
- Fixed high memory usage by gotgproto (uses around 5MBs now, earlier it was 100+ MBs)
- Rewrote GoTGProto client utilities, it should be more handy and cleaner to create a new client now.
- Added a new
dispatcher.Dispatcher
interface - Renamed
dispatcher.CustomDispatcher
todispatcher.NativeDispatcher
- Made some optimizations in command and message handlers
- Added
types.Message
, which is a union oftg.Message
,tg.MessageService
, andtg.MessageEmpty
structs. ext.Update.EffectiveMessage
is of the type*types.Message
now.- Added a new optional field in ClientOpts, named
AutoFetchReply
(setting this field totrue
will automatically castReplyToMessage
field inupdate.EffectiiveMessage
) - Peers for logged in user will now be saved in session while starting client.
- Added
client.ExportSessionString()
,client.RefreshContext(ctx)
andclient.CreateContext()
methods togotgproto.Client
. - Removed an unintentional display of session data in
Stdout
. - Added
SystemLangCode
andClientLangCode
optional fields togotgproto.Client
. - Moved helper methods errors to
errors
package (gotgproto/errors) - Added
gotgproto.Client.Stop()
to cancel the running context and stop the client. - Added
dispatcher.StopClient
handler error, which if returned through a handler callback will result in stopping the client. - Added
gotgproto.Client.Start()
to login and connect to telegram (It's already called by gotgproto.NewClient so no need to call it again. however, it should be used to re-establish a connection once it's closed viagotgproto.Client.Stop()
) - Fixed session database initialization happening twice per login.
Full Changelog: anonyindian/gotgproto@v1.0.0-beta09...v1.0.0-beta10