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
As I elaborated in #1, this approach is easy to use for the developer but breaks UX for users that were in the middle of a scene when it gets slightly updated and the step positions shift. If we store step names instead of positions that will be much more reliable (and we could even allow developers to add optional fallback steps for legacy users).
every wait() call must accept label, such as wait("name")
call() must only allowed to be made from within a labelled step when the next step (a return point) is labeled
prevent adding two labels for a single step to prevent ambiguity when discovering current step name
recognize old session format for backwards compatibility
The text was updated successfully, but these errors were encountered:
Currently, the stack frame stores the position of the step which called
wait()
:grammy-scenes/src/types.ts
Lines 12 to 17 in 84a1082
grammy-scenes/src/scenes_manager.ts
Lines 118 to 121 in 84a1082
As I elaborated in #1, this approach is easy to use for the developer but breaks UX for users that were in the middle of a scene when it gets slightly updated and the step positions shift. If we store step names instead of positions that will be much more reliable (and we could even allow developers to add optional fallback steps for legacy users).
wait()
call must accept label, such aswait("name")
call()
must only allowed to be madefrom within a labelled stepwhen the next step (a return point) is labeledThe text was updated successfully, but these errors were encountered: