Migration FAQ supplement (Finite State Machine) (#1264)

* Updated Migration FAQ > Finite State Machine * Fixed typos, added changelog * Fixed typo x2
aiogram · Aug 13, 2023 · 0cec7d4 · 0cec7d4
1 parent ac124f5
commit 0cec7d4
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/CHANGES/1264.doc.rst b/CHANGES/1264.doc.rst
@@ -0,0 +1 @@
+Supplemented "Finite State Machine" section in Migration FAQ
diff --git a/docs/migration_2_to_3.rst b/docs/migration_2_to_3.rst
@@ -112,6 +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.
+
+  Instead of this you should set states by passing them directly to
+  :class:`aiogram.fsm.context.FSMContext` (:ref:`Read more » <Finite State Machine>`)
+- State proxy is deprecated, you should update the state data by calling
+  :code:`state.set_data(...)` and :code:`state.get_data()` respectively.
 
 
 Sending Files