From ed0a53e8f9dad5b528c77d1de9a4e9f3bcea71c0 Mon Sep 17 00:00:00 2001 From: nullmatawasoradesu <119107850+wakaree@users.noreply.github.com> Date: Sun, 13 Aug 2023 22:37:42 +0300 Subject: [PATCH] Fixed typos, added changelog --- CHANGES/1264.doc.rst | 1 + docs/migration_2_to_3.rst | 9 ++++++--- 2 files changed, 7 insertions(+), 3 deletions(-) create mode 100644 CHANGES/1264.doc.rst diff --git a/CHANGES/1264.doc.rst b/CHANGES/1264.doc.rst new file mode 100644 index 00000000..b5cc6f82 --- /dev/null +++ b/CHANGES/1264.doc.rst @@ -0,0 +1 @@ +Supplemented a section Finite State Machine in Migration FAQ diff --git a/docs/migration_2_to_3.rst b/docs/migration_2_to_3.rst index 9b17710e..8a42fa5e 100644 --- a/docs/migration_2_to_3.rst +++ b/docs/migration_2_to_3.rst @@ -112,10 +112,13 @@ Finite State machine - State filter will no more added to all handlers, you will need to specify state if you want - Added possibility to change FSM strategy, for example if you want to control state for each user in chat topics instead of user in chat you can specify it in the Dispatcher. -- Now :class:`aiogram.fsm.state.State` and :class:`aiogram.fsm.state.StateGroup` don't have helper methods like :code:`set()`, :code:`next()`, etc. +- Now :class:`aiogram.fsm.state.State` and :class:`aiogram.fsm.state.StateGroup` don't have helper + methods like :code:`.set()`, :code:`.next()`, etc. - Instead of this you should set states by passing them directly to :class:`aiogram.fsm.context.FSMContext` (:ref:`Read more » `) -- State proxy is deprecated, you should update the state data by calling :code:`state.set_data()` and :code:`state.get_data()` respectively. + Instead of this you should set states by passing them directly to + :class:`aiogram.fsm.context.FSMContext` (:ref:`Read more » `) +- State proxy is deprecated, you should update the state data by calling + :code:`state.set_data(...)` and :code:`state.get_data()` respectively. Sending Files